10

Until BFT messages are deployed and working, the DPOS side of BFT-DPOS will reach finality for a transaction 180 seconds after it is included in a block. This is assuming a nominal network conditions with 21 producers. The math to arrive at this number is that, each block must be "pre-committed" to by 2/3 + 1 producers in order to be eligible for "...


3

cleos set account permission MYACCOUNT active '{"threshold": 1, "keys":[], "accounts":[{"permission":{"actor":"eosio.null","permission":"active"},"permission":{"actor":"MYACCOUNT","permission":"eosio.code"},"weight":1}], "waits":[] }' owner -p MYACCOUNT cleos set account permission MYACCOUNT owner '{"threshold": 1, "keys":[], "accounts":[{"permission":{"...


1

You can do an SHA256 of the .wasm code to see its hash, and you can verify that on chain by doing cleos get code ACCOUNT_NAME. So it wouldn't be very difficult to write a script to check that the hash is as you expect it to be before performing a transaction.


1

When you do a transaction you get the expiration time of the transaction along with the tx hash other than few other parameters. The expiration time is the time till which the tx is valid.If the tx gets included in the blockchain in block x after it is broadcasted ( this can be checked by using the command cleos get transaction txid ) , then . within the ...


Only top voted, non community-wiki answers of a minimum length are eligible