Another EthDenver conference is in the books and as expected came with an intense 2 week program around the whole web3 ecosystem, packed with more than 300 side events, parties, hacker houses, hackathons and summits. Besides the common megatrends like DePIN, AI bridges into decentralized infrastructure and the cambrian explosion of L2 and L3 technologies, Decentralized Science played a major role in Denver. Probably the most exciting track to attend was the collaboratively organized 4 day SciOS community event (a huge shoutout to NumFOCUS' John Starr and his team) that brought together nearly any company and project operating in the space) and that culminated in Desci Summit hosted at Colorado University end of the first week. Not to mention the accompanying NERD Airbnb hacker house that was organized by our friends of Desci.World Josh and Julani and that I had the privilege staying in during the whole range of the conference. One special perk of staying at the Hacker House turned out to be able to just stay at the same place but still learn about exciting new technology since many projects dispatched their Devrels and representatives to present or conduct workshops. Another one being part of the first AsaDAO in the U.S. that brought together a huge crowd of people from many corners of the space. It was particularly exciting to see how various aspects of the DeSci ecosystem start to converge. While Molecule approaches DeSci with our strong competence in fundraising, DAO operations and tokenomics, many projects focus on building infrastructure for decentralized publishing, knowledge sharing, peer reviews and decentralized journals, and of course Artificial Intelligence based tools that e.g. help solving "who said it first" use cases like Desci.World's Proof of Knowledge protocol. Web3 by its very nature is a disruptive technology stack that tries to get rid off permissions and intermediaries which opens questions of how protected IP can be captured and selectively kept secret in contrast to the bold vision of a fully open sourced science ecosystem that's primarily funded using retroactive or grant providing mechanics, such as Gitcoin Grants or Hypercerts. I had highly fruitful meetings with uprising technology stars that might turn out highly impactful for the Molecule Seed and IPNFT stacks like the schematized project description and data collection tool FirstApproval or the highly disruptive publishing and data collaboration solutions of Desci.Labs. Lastly, EthDenver of course held the main promise of an international conference that allowed me to have highly productive and very happy meets and greets with and put some faces to the Telegram handles of our valued infrastructure partners of Lit Protocol, Ceramic Network and OrbisDB Hackerhouse vibes https://x.com/DeSciWorld/status/1761939453172396436?s=20 https://photos.app.goo.gl/2sKEN253QvuSF4Zm7

User Profiling Uses orcid researcher profiles as foundation for decentralized, web3 provable profiles building on top of what retrox has achieved https://github.com/retrox-pgf-team/orcidauth/tree/arxiv-api https://orcidauth.vercel.app/register ("login with orcid")

Decentralized apps rely heavily on blockchain state to display current and historical values like an account's balance, its NFT holdings, or current exchange rates on DEXes. Projects like The Graph or Covalent make blockchain data accessible, chain indexers like Etherscan provide historical information about the chain's state, and RPC providers like Infura or Alchemy allow wallet extensions like Metamask to connect to their full-node infrastructure. However, unless you run your very own full-node you cannot prove that any value provided by these sources truly resembles the chain state they represent. In short: relying on external, centralized services imposes a trust risk. However, the way how Ethereum stores data allows trusting the chain state data without trusting the provider itself, thanks to proofs. This is how it works. Ethereum's storage model Ethereum uses a tree-based storage model that contains each account's balance and the storage for contract-based accounts. All values are wrapped in a traversable hash trie structure - a Patricia Merkle Trie - that allows creating cryptographic hash proofs for each tree node. The state root hash of a block represents the complete state of all accounts and contracts at a given block height, aka the world state. Block producers execute new transactions on their local state copy and bundle the resulting new state root hash and a list of all executed transactions into a new block. Light Ethereum clients cannot verify the current chain's state since they're not keeping a full copy of the world state. Full nodes can rebuild the state tree by executing every transaction since genesis, and then constantly update it as new blocks arrive. To save storage space they only keep the most recent chain states and hence cannot respond to state queries from the past, i.e. they're not able to determine an account's balance older than - depending on the node's settings - 64 blocks. That's sufficient to create proofs about the current state, though. Cryptographic proofs on hash trees Merkle trees use hashes of their nodes' values as keys to guarantee their content integrity. To build a simple binary Merkle tree, a prover starts by computing a hash over a node L's content h(L). Next, they compute the hash over h(L) and the hash of a sibling content node K: h(h(K)+h(L)). Using this hash as a key they create a new node KL with h(K) and h(L) as children and find another node IJ at the same tree level to create a new parent node that hashes all values of the underlying tree structure: h(IJ + KL) = h(h(h(I) + h(J)) + h(h(K) + h(L))). This process is repeated until all nodes are combined to a single root hash. Since each parent node keeps a hash of its children, it's impossible to change anything down the tree without affecting the tree's root node.

lets users sell their future stream revenue instantly workings an user receives streaming funds out of a Superfluid SuperToken stream, e.g. as the promise for the work he's doing. the user wants to early access funds that haven't been streamed to him yet the user mints an NFT containing a SuperApp interface. The SuperApp callbacks will redirect the stream sink to whoever will own the NFT. the user sets an termination date for the NFT ("holder receives funds from the stream for the next 30d") the user sells that NFT on an open marketplace (manually prices it at the value the stream will accrue until the term. date) a buyer buys that NFT from the user. The SA callback redirects the SF stream to the new owner's address.