Detailed description of your project or idea and why you believe it deserves funding:
Tezos Community Profiles (TCP) is pretty much finished. I have scraped tzprofiles and tezid for 43k profiles that I would like to boostrap the mainnet TCP contract with.
By my calculation it will cost about 2500tez to boostrap with all the data.
I am requesting 3500tez so I have a small buffer and a bit for the work.
What type of background or experience do you have and your team have in building out a project like this:
17 years as a software developer and systems architect. Worked on everything from small to major software project in a variety of languages. Used to working on open source. In Tezos ecosystem from the start. Built TezID, ChainBorn and now TCP on Tezos.
Before bootstrapping TCP I wanted to make sure it would work nicely with jstz (and potentially other rollups). jstz has built-in account abstraction, so I am currently waiting on some details about how that is meant to work.
There has also been a few other relevant things happening, of which I don’t know how much I am allowed to say There might be some news soon. I will update everyone here.
Rest assured, TCP is coming! I am just waiting for some things to come together before bootstrapping.
what’s the status of this? i missed the memo on tzprofiles shunting down completely and for my preservation efforts Kepler data is particularly vital to capturing the art ecosystem in 2022, and now extremely hard to find.
lots of anonymous artists who only verified information with tzprofiles and may not even have access to the wallets just don’t have profiles anymore. I only require json. I imagine it can’t be more than a few hundred megabytes at most.
if someone has a snapshot of any quality get a link to me on bluesky. this is not something that can get lost and my request from over a year ago to objkt to resurface this data (when it was still available) fell on deaf ears.
i’ve compiled a list of related multihashes that still exist onchain that need to remain verifiable through the bootstrap so that collectors like me know who they’ve collected from without trusting centralized companies:
So if I understand correctly, you want to have the profiles.json statically stored on mainnet as bytes or similar to be sure to be able to retrieve the data right?
Also, are the pics all still available on IPFS? If so, I can see what I can do to pin these IPFS hashes to our IPFS nodes so that they remain available.
If you have all the pictures but they aren’t available anymore on IPFS , then we can reupload them on IPFS so that they are available on the same CID’s (if they are original).
Can you upload the profiles.json to IPFS and send the IPFS hash in a reply so that we can check it out?
i think so. i dont have a good reference for what the structure looked like. the pictures i recall being centralized and im mostly after what can be verified, so computing the CIDs or the signatures if those are included.
introducing into standard ipfs is i think a possibility if blake wasnt an intentional choice to avoid that. I’m already pinning ~5TB of data from the chain so I’m perfectly willing to keep a few MB alive indefinently if it helps verify the artists I’ve collected from.
There might be some news soon. I will update everyone here.
