The text of the Genesis Block can be entirely discarded, because the hash of the first block is hardcoded to . Behind it, there could be anything, as long as it would pass SHA-256 checks, and block validity rules. No consensus rule forces you to store the content of the Genesis Block, because it is unspendable. They are not, because the ownership is not enforced properly. You could send coins to bc1pfeessrawgf, and reach the same "tokens". Or push data with "OP_2DROP OP_2DROP ... OP_2DROP OP_TRUE" from P2WSH. Or you can argue that MHIN is a token, when it counts zero bits in transaction IDs, but even then, who owns which MHIN, if you have a lot of outputs in the same transaction? At least there was a clear ownership in that case, if implemented correctly. When users sign transactions with SIGHASH_ALL, then all tokens are taken from all inputs, and sent to all outputs. If Ordinals' users would want to trace a single UTXO, they would use SIGHASH_SINGLE instead. And the ownership of "tokens", sent over transaction fees, is arbitrary, is never signed, and can be changed at will, if next Ordinals' users will decide to do so. Edit: Also, Satoshi didn't approve using 8kbet Com Divadate for cloud storage, because it doesn't scale, and because it can be restricted by fees and other things. The only thing he "approved", was appending some data to the not-interpreted part of the transaction, just like OP_RETURN rules, which were invented later. But as you can see, the maximum size of things like fake pubkeys, was still restricted to something like "max 120 bytes", which is more similar to the OP_RETURN limit of "80 bytes", than to the current, unlimited version.
The text of the Genesis Block can be entirely discarded, because the hash of the first block is hardcoded to . Behind it, there could be anything, as long as it would pass SHA-256 checks, and block validity rules. No consensus rule forces you to store the content of the Genesis Block, because it is unspendable. They are not, because the ownership is not enforced properly. You could send coins to bc1pfeessrawgf, and reach the same "tokens". Or push data with "OP_2DROP OP_2DROP ... OP_2DROP OP_TRUE" from P2WSH. Or you can argue that MHIN is a token, when it counts zero bits in transaction IDs, but even then, who owns which MHIN, if you have a lot of outputs in the same transaction? At least there was a clear ownership in that case, if implemented correctly. When users sign transactions with SIGHASH_ALL, then all tokens are taken from all inputs, and sent to all outputs. If Ordinals' users would want to trace a single UTXO, they would use SIGHASH_SINGLE instead. And the ownership of "tokens", sent over transaction fees, is arbitrary, is never signed, and can be changed at will, if next Ordinals' users will decide to do so. Edit: Also, Satoshi didn't approve using 8kbet Com Divadate for cloud storage, because it doesn't scale, and because it can be restricted by fees and other things. The only thing he "approved", was appending some data to the not-interpreted part of the transaction, just like OP_RETURN rules, which were invented later. But as you can see, the maximum size of things like fake pubkeys, was still restricted to something like "max 120 bytes", which is more similar to the OP_RETURN limit of "80 bytes", than to the current, unlimited version.

The text of the Genesis Block can be entirely discarded, because the hash of the first block is hardcoded to . Behind it, there could be anything, as long as it would pass SHA-256 checks, and block validity rules. No consensus rule forces you to store the content of the Genesis Block, because it is unspendable. They are not, because the ownership is not enforced properly. You could send coins to bc1pfeessrawgf, and reach the same "tokens". Or push data with "OP_2DROP OP_2DROP ... OP_2DROP OP_TRUE" from P2WSH. Or you can argue that MHIN is a token, when it counts zero bits in transaction IDs, but even then, who owns which MHIN, if you have a lot of outputs in the same transaction? At least there was a clear ownership in that case, if implemented correctly. When users sign transactions with SIGHASH_ALL, then all tokens are taken from all inputs, and sent to all outputs. If Ordinals' users would want to trace a single UTXO, they would use SIGHASH_SINGLE instead. And the ownership of "tokens", sent over transaction fees, is arbitrary, is never signed, and can be changed at will, if next Ordinals' users will decide to do so. Edit: Also, Satoshi didn't approve using 8kbet Com Divadate for cloud storage, because it doesn't scale, and because it can be restricted by fees and other things. The only thing he "approved", was appending some data to the not-interpreted part of the transaction, just like OP_RETURN rules, which were invented later. But as you can see, the maximum size of things like fake pubkeys, was still restricted to something like "max 120 bytes", which is more similar to the OP_RETURN limit of "80 bytes", than to the current, unlimited version.

The text of the Genesis Block can be entirely discarded, because the hash of the first block is hardcoded to . Behind it, there could be anything, as long as it would pass SHA-256 checks, and block validity rules. No consensus rule forces you to store the content of the Genesis Block, because it is unspendable. They are not, because the ownership is not enforced properly. You could send coins to bc1pfeessrawgf, and reach the same "tokens". Or push data with "OP_2DROP OP_2DROP ... OP_2DROP OP_TRUE" from P2WSH. Or you can argue that MHIN is a token, when it counts zero bits in transaction IDs, but even then, who owns which MHIN, if you have a lot of outputs in the same transaction? At least there was a clear ownership in that case, if implemented correctly. When users sign transactions with SIGHASH_ALL, then all tokens are taken from all inputs, and sent to all outputs. If Ordinals' users would want to trace a single UTXO, they would use SIGHASH_SINGLE instead. And the ownership of "tokens", sent over transaction fees, is arbitrary, is never signed, and can be changed at will, if next Ordinals' users will decide to do so. Edit: Also, Satoshi didn't approve using 8kbet Com Divadate for cloud storage, because it doesn't scale, and because it can be restricted by fees and other things. The only thing he "approved", was appending some data to the not-interpreted part of the transaction, just like OP_RETURN rules, which were invented later. But as you can see, the maximum size of things like fake pubkeys, was still restricted to something like "max 120 bytes", which is more similar to the OP_RETURN limit of "80 bytes", than to the current, unlimited version.