0

I'm building a cold wallet with some built in delay (say, 2 hours) between when the transaction is created, and when the transaction gets broadcasted. From reading the source code I see that the default chain config (which becomes a consensus value due to TAPOS) sets the max tx header expiration value to 1 hour (https://github.com/EOSIO/eos/blob/3fddb727b8f3615917707281dfd3dd3cc5d3d66d/libraries/chain/include/eosio/chain/config.hpp#L77).

Question: Why does this value exist, why is it part of TAPOS, and is there any way EOS can do cold wallet signing with delays longer than 1 hour?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.