Row 22052

Row ID: 22052 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 22052 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

Imagine not even needing the UTXO set. When you receive a transaction you can just check the latest global state root, which is basically a hash of a recursive zk proof that the entire chain is valid, and you can use information from the transaction to construct a proof that the transaction itself is valid, and know if it's already been included in the current state root.

That said, I'm super excited for UTXO commitments. This is my first time hearing about them, but that absolutely does sound like an awesome step.

Most L2s are pretty fucked at the moment (mostly thinking in terms of ETH L2s). Mostly due to centralized sequencing. Even L2s in their final form, the users will be at the mercy of the sequencing mechanism and the data availability mechanism, but even then users will still be able to get their money out, thought it might some time and high fees to do it.

The ultimate goal of Ethereum is to take one of these L2 technologies that are being deployed, and enshrining it on L1, then rebasing the entire network to be an L1 rollup, so yes, in that sense it would all just be an L1 :-)

FieldValue
text Imagine not even needing the UTXO set. When you receive a transaction you can just check the latest global state root, which is basically a hash of a recursive zk proof that the entire chain is valid, and you can use information from the transaction to construct a proof that the transaction itself is valid, and know if it's already been included in the current state root. That said, I'm super excited for UTXO commitments. This is my first time hearing about them, but that absolutely does sound …
label r/btc
dataType comment
communityName r/btc
datetime 2024-05-21
username_encoded Z0FBQUFBQm5Lak1BUmp0dnA3cEZqWUVjTGtzczl6cmZYbWJHN3g5Skp2d0ZOcUl0UER5eEZzYW13bExMYlRlWFRZS3luUlZQNXZWQ2ZhSU1sXzUwdHBrZ29KeTA3NTh5VUE9PQ==
url_encoded Z0FBQUFBQm5Lak9Qem55NjdLOTg5RlNNd0w3QUtRQmxRZkxEOXlmM01OMDZiYU8zMUNEM01VQ0NhR1FTb1lPSnpBVXdGRURNc2lNTWFUZnNqdkxlTFNWOXYwU1F4MU1QUV9WeHNnV1dncm1yQ0V2LUtoRWpPdmNrMk9tWFZUdl9YbS1Gd2FvaXFYY3k4YzR6SWV6eUg2dEhfcUU3LTJ6N0VFdktZRTJFTjNKQ2hjR2dnZjFMNHNjRUU4emdPbEZ6Zk1TZnJ0bFg1MTFVQi1obGVNeTJGUU41M2NRVWU4UFllUT09

Raw Record

{
  "text": "Imagine not even needing the UTXO set. When you receive a transaction you can just check the latest global state root, which is basically a hash of a recursive zk proof that the entire chain is valid, and you can use information from the transaction to construct a proof that the transaction itself is valid, and know if it's already been included in the current state root.\n\nThat said, I'm super excited for UTXO commitments. This is my first time hearing about them, but that absolutely does sound like an awesome step.\n\nMost L2s are pretty fucked at the moment (mostly thinking in terms of ETH L2s). Mostly due to centralized sequencing. Even L2s in their final form, the users will be at the mercy of the sequencing mechanism and the data availability mechanism, but even then users will still be able to get their money out, thought it might some time and high fees to do it.\n\nThe ultimate goal of Ethereum is to take one of these L2 technologies that are being deployed, and enshrining it on L1, then rebasing the entire network to be an L1 rollup, so yes, in that sense it would all just be an L1 :-)",
  "label": "r/btc",
  "dataType": "comment",
  "communityName": "r/btc",
  "datetime": "2024-05-21",
  "username_encoded": "Z0FBQUFBQm5Lak1BUmp0dnA3cEZqWUVjTGtzczl6cmZYbWJHN3g5Skp2d0ZOcUl0UER5eEZzYW13bExMYlRlWFRZS3luUlZQNXZWQ2ZhSU1sXzUwdHBrZ29KeTA3NTh5VUE9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9Qem55NjdLOTg5RlNNd0w3QUtRQmxRZkxEOXlmM01OMDZiYU8zMUNEM01VQ0NhR1FTb1lPSnpBVXdGRURNc2lNTWFUZnNqdkxlTFNWOXYwU1F4MU1QUV9WeHNnV1dncm1yQ0V2LUtoRWpPdmNrMk9tWFZUdl9YbS1Gd2FvaXFYY3k4YzR6SWV6eUg2dEhfcUU3LTJ6N0VFdktZRTJFTjNKQ2hjR2dnZjFMNHNjRUU4emdPbEZ6Zk1TZnJ0bFg1MTFVQi1obGVNeTJGUU41M2NRVWU4UFllUT09"
}
Explore Dataset Explore Row

Entry Information