Closed EdsonAlcala closed 1 month ago
@EdsonAlcala I would suggest to just use any
API in this case:
I don’t see value in adding a dedicated method for raw-transactions specifically. I believe any
should cover it well, so I will close this issue, but if you disagree, please, reopen it
Hello, I'm currently working in a chain signatures library to create transaction payloads for multiple Blockchains (including Near itself).
As part of the omni library, I included a way to build a signed payload for Near transactions that can be propagated.
Source: https://github.com/EdsonAlcala/omni-transaction-rs/blob/master/src/near/near_transaction.rs#L37
In the image above, if you notice, the return type of
build_with_signature
is a Vec< u8 >. Then if I want to send it to a Near network using near-jsonrpc-client-rs, it won't be possible (or perhaps I'm missing something). But I saw thatsend_tx
only accepts aSignedTransaction
. However my transaction payload is already signed.So I thought about adding a
send_raw_tx
, that only encodes to base 64 and send the payload to the network.Source: https://github.com/near/near-jsonrpc-client-rs/commit/613a0b2fcb7667da4ab8a5eceb84dd6cc2e4386a
Notice the
encode_signed_transaction
function:You can see how I used it here https://github.com/EdsonAlcala/omni-transaction-rs/blob/master/tests/near_integration_test.rs#L91.
So my goal with this issue is:
Thanks