hyper

hyper - one API... many services

⚡️ Join the hyper community

[🐘🔗 sam.arweave.dev @samecwilliams]

Huge shift here. Thanks to everyone on the @OdyseeTeam, @dh_association, and @fwdresearch teams who made this possible -- as well as @ar_io_network for all their help in the transition.

But what does this shift mean?

tl;dr: Arweave dot net now runs on AO-Core. So...

1⃣ Every response from .net is now verifiable, right to the end-user. This is the fundamental building block of decentralization. When you get a reply from an AO-Core node its headers contain everything that you need in order to verify the data atomically. No need for consensus, querying multiple nodes, etc., just fully trustless cryptographic verification.

Additionally, all of the useful tags and metadata that have always been attached to content on Arweave is now available to callers. Users can now process this information and act upon it, just like 'body' data. You can think of Arweave as a permanent database, with each item being a row. Now the whole content of each of those rows can be accessed by users, not just the largest field.

2⃣ Data served from .net is now directly sourced from Arweave nodes. Previously, there needed to be caches in between the user and the nodes, which made gateways heavier to run and 'separated' from the dataset. This detachment introduces points of software and operations dependence in the caches themselves. While .net is still importing some of the data from the legacy gateway (and will be over the next few weeks), these caches have now been removed from the data serving flow. This also opens the opportunity for...

3⃣ ...Permissionless nodes operating .net. Because each AO-Core node serves everything needed to verify each response it gives by default, the next step is to let anyone register to provide the data for IDs to the gateway, then verify their responses before relaying them to users.

This alone is a big deal. In time we expect it will provide an additional incentive for Arweave miners to serve (and also store) data, as well as improve performance (by routing to and rewarding the fastest providers) and reliability (by removing points of failure).

Further down the track there is a clear path to even decentralizing the operation of these verification+routing nodes, so that every Arweaver can take part in running those, too. We can achieve this by letting TEE nodes register with one another and share private TLS credentials, allowing them to directly serve end-user traffic routed by the DNS layer. We have tests of this flow working in principle, but principle -> practice-at-scale will take some time.

4️⃣ Compute-Over-Arweave-Data just dropped. AO-Core is a protocol to orchestrate a decentralized supercomputer. In this deployment we are making heavy use of AO-Core's codec devices, but it is now possible to do so much more than that. More on this soon.

Upshot? Decentralization and trustlessness of data access on Arweave just took a huge leap.

Trustless verification of content ->
Permissionless data serving ->
Decentralization of data access and transformation.

Congrats again everyone 🫡.

[Mason @MattMason]

Getting a lot of questions - we’ve released zero details on $ACTION by design. Whitepaper is coming. It will run on @aoTheComputer + @ArweaveEco

We chose AO because once we understood it, everything else felt like legacy tech

Excited to share more when ready 🪩

[Rohit @ropats16]

Announcing Hacker Hangouts, a new podcast spotlighting projects on @ArweaveEco & @aoTheComputer! 🎙️

Premiering tomorrow with @kadar1, founder of @AstroUSD, demoing Quantum, a bridge connecting Arweave & AO!

⏰ 8 PM IST/ 10:30 AM PST

📍 https://t.co/LC2QoWwc54

[Kyle_13 ⓐ @kylewmi]

⚫️Heads up, devs!

Don’t miss the @autonomous_af AO Ecosystem Tooling series—it’s got all you need for building in the AO ecosystem

❶ Ownable Package
❷ Process/Smart Contract Testing Framework
❸ Subscribable Package

Check out the GitHub code, demos, and more. Full details in the thread.👇

[ao @aoTheComputer]

$10 million in additional funding now available to builders in our ecosystem thanks to @SevenXVentures @everVisionHQ and @_BuilderDAO! 👀

[Outcøme @outcome_gg]

6 Billion transactions on @ArweaveEco by its 6th Birthday. Resolved as IN!

84% were right. Can you do better..?

Claim your free tokens and let's predict the future of ao together! 🔮

IYKYK https://t.co/1acE2aNVFb

#technology #resolved_market #outcome_gg

[ao @aoTheComputer]

The rules of web3 gaming have changed.

With ao, fully onchain multiplayer 3D games are now within reach. Tune in with @PSkinnerTech as he breaks it down.

[ao Builders @ao_builders]

A new era of smart contract programmability built on top of Arweave is about to start.

Save up the date! 👀

[🐘🔗 ar://vilenarios @vilenarios]

SEC ETF doc is 326KB.

So to celebrate this big day in $BTC history, its now unruggably stored on @ArweaveEco (using @ardriveapp) and accessible via hundreds of @ar_io_network gateways using an easy to remember ArNS name.

https://t.co/uIrlaI1n6h

[🐘🔗 sam.arweave.dev @samecwilliams]

🎅

https://t.co/QLtdRXA9Co

[🐘🔗ArDrive.ar.io @ardriveapp]

ArDrive does not collect or store any personal user data when using our platform 🫡🐘 the only feedback we get comes with your consent.

Please consider taking the time to fill out this survey about ArDrive and what we can do to make it better!

https://t.co/nRIAK78bgm

[Archie Whitford @ahrwhitford]

Creative Capital - enabled by revenue streams directly tied to Content ID through atomic assets on @ArweaveEco.

1) Improved capital efficiency for creators. Create more and better content today by borrowing creative resources from your revenue streams generated tomorrow.

2) Guarantees of financial attribution. Royalties and other revenue streams guaranteed to flow to the creator via content attribution and licenses enshrined in code.

3) Financial security for creators. The 'starving artist' of yesterday can feed themselves by creating futures markets on the value of their content.

A fully functioning capital system for information and content that lives forever on the permaweb 🐘

[🐘🔗 sam.arweave.dev @samecwilliams]

Arweave was built to make book burning impossible.

@thealexarchive was built to let you sponsor uploads to Arweave's archive.

@OurBazAR lets you trade those sponsorships, via @warp_contracts.

Collectively, they are a data preservation incentive stack.

[Community Labs @CommunityLabs]

We are building some exciting projects here @CommunityLabs 🤩

Join the Community Labs team for our first monthly BuildARs Space this Friday at 10AM EST. Hear from @martonlederer, @lorimer_jenkins, and @iamsaikranthi about the new and exciting projects coming down the pipeline 🧱 🛠️

Be sure to set a reminder ⏰ 📆
https://t.co/0HOCPzr6Ci

[🐘🔗 sam.arweave.dev @samecwilliams]

@ArweaveSCP In theory you can use the UCM to swap any tokens, but the first interface (built by the @thealexarchive crew) focuses on atomic assets 🙂

[🐘🔗 sam.arweave.dev @samecwilliams]

The Uniswap of the Arweave ecosystem just dropped.

[Only Arweave @onlyarweave]

.@DMacOnArweave is live and doing one of the many things he does well - providing learning opportunities.

A great intro to the Universal Data License on #Arweave.

Join in here: https://t.co/SDOIumnATR

[Forward Research @fwdresearch]

Perhaps the most immediate use case for Arweave is to permanently preserve human history and culture on the internet.
@thealexarchive is a leader in this effort, and to date has preserved more than 6 million digital artifacts from diverse sources.
How does it work? 🧵👇

[🐘🔗 sam.arweave.dev @samecwilliams]

In cyberspace:

Data -> Speech.
Identity -> Voice.

Arweave is the machine with a constitution that guarantees your right to them.

https://t.co/C5i2UZk5Hm

[hyper @_hyper_io]

Technical Debt is north of 40%; what does this mean in developer terms? Half of your day as a developer is to keep the lights on, and the other half is to build solutions to client problems.