SOULBOUND

i finally managed to publish the full documentation for the soulbound hook. i know it took longer than expected, but i spent the last few hours auditing the hook myself and looking for potential bugs, edge cases, and mistakes before making everything public. this was the third time i went through the entire thing. i’ve also been thinking about open-sourcing some of my other projects, including singularity and the llm experiment, but i want to think that through a bit more before making a decision. as always, i’m happy to hear feedback, suggestions, audits, and potential improvements from people who resonate with this kind of work. and just a small note: AI is great, but not always when it comes to writing smart contracts. meanwhile, i’m going back to fixing the website. github.com/iamdanielwss/s…

a quick note. chrome is currently showing a false positive warning on soulbound.zip. this is related to the .zip tld, which google tends to flag automatically on newer domains. it has nothing to do with the protocol itself. the review has already been submitted and should be resolved within the next 24–72 hours. in the meantime, i’m buying a new backup domain right now. we’ll share the new address as soon as it’s live. also, sorry for the delay on the documentation. the github repository with the full technical breakdown is coming in the next 2 hours.

the vision

i’ve written a new article on the blog. it covers the vision behind soulbound and some of the updates currently being built. give it a read if you’re interested in where this is heading. soulbound.zip/blog/the-ecosy…

your LP, leveraged against itself, three times over. the receipts can never leave. welcome to soulbound.

everything is now live, working, and fully compatible. every function on the website is available. why did it take so long? building and deploying production-ready v4 technology isn’t a one-click process. it means days of coding, testing, debugging, and wiring everything together. a complex hook like this has to be integrated with the frontend, and a lot of those edge cases simply can’t be tested until the system is live. a github repository is coming in a few hours with detailed documentation for anyone interested in the technical side. from now on, forever means forever. thanks if you still here. soulbound.zip

forever is forever. CONTRACT: 0xa537c034cD16F8eeBEfD0d2b16D523Bb4feBE4b7 HOOK v4: 0x5B845eD470F82a38E63F73e5dDf251C09b406aCc soulbound.zip

@ArchChaudhury @PGarimidi @cdixon @Tim_Roughgarden @skominers Make the governance tokens soulbound and I'd be happy.

6 months ago i knew almost nothing about crypto. i spent every day learning. late nights, endless rabbit holes, reading code, understanding protocols, trying to figure out why some things work and others don’t. then i discovered uniswap v4. the moment i understood hooks, something clicked. for the first time, it felt like liquidity itself could become programmable. one question kept coming back: what if liquidity could do more than just sit there? that question became SOULBOUND. a protocol built on top of uniswap v4 where your position remains yours. no managers. no custody. no one making decisions for you. your position is represented through ERC-6909. one hook. one token. no admin. no kill switch. i’m not going to explain everything today. some things are better understood by watching them unfold. this is just the beginning. v4 hook in. ERC-6909 out. follow the journey: @soulboundzip