if your TX has an expiry, then a reorg is potential death to your transaction. You then need to create a new version of it with a new expiry date, forcing you to sign a new TX with mostly the same contents, with the same key. Even though it's been arbitrated before. This is wrong
-
-
“New transaction broadcasts do not necessarily need to reach all nodes” is an argument for my case, not against. If your TX doesn't get broadcast well enough, it may take longer before it's arbitrated (as it reached less miners), meaning the expiry becomes more reorg critical.
1 reply 0 retweets 0 likes -
I wanna send BTC, but for reasons I can't be near the device when it sends the TX so there's need for delay, consequently the key needs to be destroyed after signing TX: one-time-use. I keep TX data in case device compromised->new broadcasting setup. ZCash can no longer do this.
1 reply 1 retweet 0 likes -
What do you mean no connection? I'm saying ZCash doesn't work if you're in a privacy critical situation where you don't want to broadcast a TX until you've removed yourself from the geographical location. There's all the reasons to allow this, and no good reason to deny this.
2 replies 0 retweets 0 likes -
I dont see how nodes become less stable with higher mempool usage. They have a max size for the mempool, assuming that's something they didn't change when forking BTC. The whole reason to optimize the mempool is to prevent annoying loss of TX's, which TX expiry does explicitly...
1 reply 0 retweets 0 likes -
And I wasn't pulling it out of thin air that such suggestions have been shot down before: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-March/007734.html …
1 reply 0 retweets 0 likes -
A TX once valid becoming invalid is exactly the issue here. Is in ZCash the expiry part of what's signed or not? If yes, that's in the mined block and the issue stands. If not, the whole ZIP is useless extea bandwidth usage in the face of nodes determining their own TTL on TXs.
1 reply 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.