Closed vsubhuman closed 6 years ago
Tx serialisation tested locally and works as expected (compared to this endpoint - https://explorer.adalite.io/api/txs/raw/9253c2be3a42e9552721715a52aa305c1576b37a80c0adc3f31d2e3d8c7c87aa)
The only thing left to test is whether the transaction with the extra-long address is successfully stored in the tx_body
column. Couldn't test it yet, because of local docker problems, but intuitively it's expected to work fine.
Finally tested the tx_body
of the super-long transaction.
Ready for merge. @nicarq, we gotta discuss the creation of the (tx_body text)
column in the production.
Closes #2
tx_body text
to the SQL DB-init scriptserialize'
to create the raw tx right in the txs table module. No API has changed.Serokell.Util.Base16
to convert serialised txs to stringsP.S
cutDownLongAddress
that was added in another PR