|17 Sep 2019|
In reply to yes, WP outlines privacy roadmap
In reply to HermanSomeone else asked about that lol
|02:18:51||CryptoMedication||I asked about how the protocol is able to determine whether I double spent or not|
|02:19:05||CryptoMedication||Since it apparently does not need any address / sender data|
|02:19:39||CryptoMedication||Seems like it’s “scaling” by increasing the barrier to actually use the protocol. Which is a backdoor, convoluted way to do so|
|02:20:32||CryptoMedication||But not even ^ because you said only 1 TX per block (and in mempool), which makes me wonder what would stop someone from sending a diff TX to multiple nodes (with known connections)|
|02:21:12||Herman||You're clearly not familiar with protocol, yet have conclusive opinions on it 🤔|
|02:21:47||Herman||accounts send transactions (called operations) to other accounts.. accounts are addressed by a number|
|02:22:11||Herman||every time an account authors an operation, a field inside the account is incremented, called n_operation|
|02:22:30||Herman||a double-spend is detected by two different transactions using same n_operation|
|02:23:17||CryptoMedication||What you explained is incomplete|
|02:23:46||CryptoMedication||Bitcoin is UTXO. Ethereum is state-based. They both have two diff means of accounting for whether someone is double spending|
|02:23:59||Herman||Pascal is state-based|
In reply to HermanWhat you described sounds somewhat like a combination, but not really.
“n_operation” doesn’t really tell us anything.
Are the coins non-fungible? If so, we’re getting somewhere.
If not, can you explain what “n_operation” means?
|02:25:02||CryptoMedication||Perfect. So the entire state is stored then ...|
|02:25:10||Herman||n_op is a counter incremented everytime an account authors an operation|
|02:25:20||CryptoMedication||The nonce. I hear you|
|02:25:23||CryptoMedication||Making sense now|
|02:25:24||Herman||the state of accounts is stored in the SafeBox|
|02:25:46||Herman||It's not a "nonce" per say, it's a counter|
|02:26:20||CryptoMedication||So how does one join the network w an account? Since there is a payment required|
|02:27:21||CryptoMedication||Are the contents of the safebox known?|
|02:28:29||CryptoMedication||I see. I’m assuming all account segments are SHA256 hashed?|
|02:29:59||Herman||yes in version 5 the SafeBox Hash is the merkle-root of the account segment hashes|
|02:30:21||Herman||account segment hashes is a rolling hash of account hashes (should be merkle-root too, but not designed that way)|
|02:32:41||Herman||version 6 the size of account segments will be dynamic, currently fixed at 5|