Content pfp
Content
@
https://warpcast.com/~/channel/arweave
0 reply
0 recast
0 reaction
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
Ouch 🥲It looks like smartweave has no future on /arweave Seems @redstone-oracles has wound down support for their Warp implementation. https://academy.warp.cc is down and so is the sonar explorer 🥹 ...and I'm petty sure the WarpSDK is dead too 😭 I'm going to have to migrate it all An elephant never forgets 🐘
2 replies
0 recast
3 reactions
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
It was nice while it lasted, but now we must migrate the herd. DJ play me out with - Video Killed The Radio Star. https://open.spotify.com/track/6t1FIJlZWTQfIZhsGjaulM
1 reply
0 recast
2 reactions
JonnieSparkles pfp
JonnieSparkles
@jonniesparkles
Swing them over to AO, its where all the cool elephants are!
1 reply
0 recast
3 reactions
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
So yeah about that, I used to be excited about /ao until I started building on it. The first important thing is how "state" works on AO, - smartweave was stateless and the whole idea of lazy evaluation paired well with our axiom of "Don't trust; Verify". Now since AO is stateful, here is what it implies • Apps just trust the results of state evaluation from AO's MUs, SUs and CUs; this is just web2, nothing new here, already get that with cloudflare + AWS • Or mabye apps want to evaluate state themselves from the logs to verify results returned from AO; we've been there, it's smartweave, no need for MUs, SUs and CUs • Or maybe apps don't want to evaluate state themselves, so they request more CUs to check each other's work and hold each other accountable; well isn't that PoS. you would be either be building out your own PoS network of CUs, or trying to use existing public networks like Ethereum or Solana for compute on AO. Still not infinitely scalable, plus it's a lot of work.
1 reply
0 recast
1 reaction
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
Also, it assumes that you would be adding your own incentive mechanism, otherwise, why would any of the units care about messages from your app. So essentially, one ends up bringing all the other parts of a blockchain to use AO and AO only comes with Arweave's permanent storage with somewhat weak security guarantees. I'm not saying that it's not the right way to do it. I'm just saying It's the same /cosmos appchain thesis but from the POV of /arweave. IMO the rollup architecture is a preferred way of doing appchains and I believe this because of how much adoption the idea of smart contracts have gotten. Smart contracts are how developers (esp solo devs) can build really decentralized applications without having to recruit an army on nodes to run his app and keep it decentralized (ie distributed nodes and consensus). @heliumfoundation use to work like that, but now they are smart contracts on /solana. https://warpcast.com/ichristwin.eth/0x3cd5c811
1 reply
0 recast
1 reaction
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
With rollups, devs can still build chains (or other offchain systems) as smart contracts onchain. No node distribution or consensus needed, and that's what I believe developers need. A don't want to launch a consensus protocol for every web3 app I build. That dosn't scale, and is way too much work. What I could try is take our smartweave contract and turn that into a minimal stateless zk-validity rollup on /ethereum with an architecture inspired by @taikoxyz ...but with no bridge, no human user, no chainId, no state, just smart meters and a "Half Adder" zk circuit. The sums from the meters can be posted to a contract on @ethereum and written to state if validity proof is accepted. raw inputs can be posted to it's DA. Would retain /arweave for permanent storage. So maybe it goes like this: [Meter] ⮩ MU (Arweave storage) ⮩ custom SU (m3ter-chain sequencer) ⮩ custom CU (zk prover & block proposer) ⮩ Ethereum L1 (verifiable state) And that's how we build on AO 👀
1 reply
0 recast
1 reaction
JonnieSparkles pfp
JonnieSparkles
@jonniesparkles
Very insightful posts - you should share this with the broader community for feedback! I wish I was technical enough to give it a more thoughtful reply but I will share with the team as well. Curious for their take. You have to do what is best for your project and regardless of your decision, I wish you the best :)
1 reply
0 recast
1 reaction
I. Christwin〔▸‿◂〕💡 pfp
I. Christwin〔▸‿◂〕💡
@ichristwin.eth
Whom would you recommend I share this with for said feedback? ...the /arweave channel here is a relatively nascent community. I could imagine the rest of us are hanging out in some AO chatroom out there 😅
1 reply
0 recast
0 reaction
JonnieSparkles pfp
JonnieSparkles
@jonniesparkles
Arweave eco tends to be more active on Twitter and Discord than here. I'll give it some thought and get back to you! We're launching ar.io mainnet today so a bit scatter brained prepping for that. Would love your support!
1 reply
0 recast
1 reaction