Currently, $HASH requires a few key centralized infrastructural components to keep the project running. In my mind, it is critical to consider and develop a strategy for HASH to live well beyond POB studios. To address the most pressing centralized parts: we would like to look into a path to decentralizing the token metadata system:
tokenURI: this currently points to pob.studio/api/token-metadata?id=<token-id>
Motivation
As an artist, I strongly believe that the art should (if the medium enables as such) live beyond the creators. The Ethereum blockchain is such a medium that lives as long as the consensus holds. With this, the current cruxes on centralized lambdas can prove to be fatal to the project if were to fail or deactivated.
With this in mind though, POB studios do enjoy the capacity to deliver 'over the air' updates to the metadata system; this has allowed for a number of features to be easily surfaced and delivered to the community.
Example, with the new token metadata feature, we added NO. XXX as a trait to allow buyers and sellers access to that metadata when appraising the asset.
We do not intend to 'give up' the capacity to modify this metadata, (maybe in the future this power is given to a historians DAO or simply relinquished), but we do believe this part of our infrastructure should be more 'robust' and decentralized.
Rationale (if a suggestion is proposed)
This change will be an ongoing topic for POB.studios and HASH. As the project matures, decentralization become an ever more pressing requirement. To address this, we will need to work with the current constraints of the POB architecture and metadata users (opensea, rarible).
Implementation
This HCIP is a call for developer(s) interested in drafting spec + implementing such a system for the HASH community.
Developers will note that we make a few (via a multicall contract) calls to the respective registry contracts: HashRegistry, TokenMetadataRegistry, and the ERC1155. We also make calls to the blockchain to fetch all the corresponding tx data.
Some open questions on decentralization:
Can this data be statically served on IPFS or Arweave? (issue with the token-metadata registry though)
If not, and requires some amount of just-in-time computation? Can this be decentralized in any way?
How can some administrator (POB.studios) operate this and make updates to the system?
Designated team: UFG
Sponsor: POB studios
We will be funding development (via a 5 ETH grant, subject to more), providing access to repos, and shipping w/ the designated team this upgrade.
Summary ( 2-5 Sentences )
Currently, $HASH requires a few key centralized infrastructural components to keep the project running. In my mind, it is critical to consider and develop a strategy for HASH to live well beyond POB studios. To address the most pressing centralized parts: we would like to look into a path to decentralizing the token metadata system:
tokenURI: this currently points topob.studio/api/token-metadata?id=<token-id>Motivation
As an artist, I strongly believe that the art should (if the medium enables as such) live beyond the creators. The Ethereum blockchain is such a medium that lives as long as the consensus holds. With this, the current cruxes on centralized lambdas can prove to be fatal to the project if were to fail or deactivated.
With this in mind though, POB studios do enjoy the capacity to deliver 'over the air' updates to the metadata system; this has allowed for a number of features to be easily surfaced and delivered to the community.
Example, with the new token metadata feature, we added
NO. XXXas a trait to allow buyers and sellers access to that metadata when appraising the asset.We do not intend to 'give up' the capacity to modify this metadata, (maybe in the future this power is given to a historians DAO or simply relinquished), but we do believe this part of our infrastructure should be more 'robust' and decentralized.
Rationale (if a suggestion is proposed)
This change will be an ongoing topic for POB.studios and HASH. As the project matures, decentralization become an ever more pressing requirement. To address this, we will need to work with the current constraints of the POB architecture and metadata users (opensea, rarible).
Implementation
This HCIP is a call for developer(s) interested in drafting spec + implementing such a system for the HASH community.
Our current lambda
Developers will note that we make a few (via a multicall contract) calls to the respective registry contracts: HashRegistry, TokenMetadataRegistry, and the ERC1155. We also make calls to the blockchain to fetch all the corresponding tx data.
Some open questions on decentralization:
Designated team: UFG
Sponsor: POB studios
We will be funding development (via a 5 ETH grant, subject to more), providing access to repos, and shipping w/ the designated team this upgrade.
Notes
Token metadata registry https://etherscan.io/address/0x9071044edcAFB1693b5E8b9734B7943F3AE9F6AA
ERC1155 Contract https://etherscan.io/address/0xE18a32192ED95b0FE9D70D19e5025f103475d7BA
Hash registry https://etherscan.io/address/0x29ca58d4a0857Ae3F0608a546cdE5f254A3F867a
Sample call to the API
https://pob.studio/api/token-metadata?id=0x80000000000000000000000000000002000000000000000000000000000003d7IPFS gateway:
https://github.com/proofofbeauty/gateway