Arweave Ecosystem Weekly Report #59: The ‘Booting the Permaswap’ Edition

0 412

With only one week left until Arweave in Lisbon, things started to heat up within the ecosystem: everVision just released Permaswap’s testnet – so the promise for an Arweave native DEX is closer than ever to being fulfilled. ArDrive Team rebranded to AR.IO as a statement for the multilateral work they conducted in the past year, and Akord unleashed the potential of big uploads. 

These are only some of the headlines. Do you want to know more?

I. Arweave Network

Arweave 2.6 implementation gets closer with each passing day, so we started to ask relevant members from the Arweave dev community about certain features that the 2.6 version will enable. The first “stop” was to find out how Arweave’s security and power consumption would be improved by a single feature. Here you have some of the highlights of an interview with DMac.

Q: We are willingly restricting [with 2.6 version] the hash rate to around 800/s/node to stop the expensive “arms race” favouring costly machines rather than efficient machines for the task at hand: replicating Arweave’s data set. So, what’s the “catch”? How can Arweave remain viable from a security standpoint and still curve down the hashrate?

It’s because it’s no longer just hashing. There’s “useful work” being done for each hash. With 2.6 there’s a maximum amount of hashes a single replica of the arweave data set will generate… to get access to all those hashes, you have to store 100TB of data, and you have to get that data from the network.. taking several days. If you wanted to generate a 51% attack, you’d have to be storing 51% of the replicas on arweave in a simplified situation… there are 1000 replicas of the data stored by miners (And that’s just the hypothetical amount of replicas.. I’ve seen Sam quote a number in the 4000s), each one 100TB in size. That means the total amount of storage is … I don’t even know…quite a lot of PetaBytes? […]

Assuming the number of miners stays about the same and the weavesize grows.. an attacker will have to sync and store more and more data if they want to attack the network.

Q: Returning to the subject at hand – the green side of 2.6. Can you estimate how many Watts/h an optimised miner could consume?

A: Yeah, [although] I’m not a miner…at the beginning, when Arweave was pure PoW, it could be a LOT, computing billions of hashes. With SPoRA, it went to thousands…with 2.6 it went to hundreds. A laptop CPU can do millions per second, so really, the power is using – some small portion of a consumer-grade CPU and then running SSDs at full speed 24h a day. SSDs are pretty efficient power wise though…because they have no moving parts, so you might say a full replica is 25 of 4TB SSDs and SPoRA (Arweave 2.5) lets you run them all at max transfer speed.. if you have enough CPUs. So.. before.. with a full replica.. and 25 4TB SSDs, all recalling chunks at 7300 MB/s you could keep a lot of CPUs busy. Now (with Arweave 2.6), even with that same hardware, you wouldn’t be able to use one CPU fully.

Now, this is only a teaser for the full material, which will be released in the following days. Still, we believe that it’s more than enough to have an idea of how “SPoRA with a limit” has the potential to improve the overall security of the network in a PoW fashion (more a proof of useful work actually), but with hardware and power consumption that is rather found in PoS networks.

II. Arweave Ecosystem

Arweave in Lisbon

Almost a week left until Arweave in Lisbon event. Arweave’s core team and a bunch of projects from the ecosystem will be present there – what about you? Arweave’s presence in Lisbon is structured in three main events:

On 29 October, there will be the devDAO x Arweave Ecosystem Happy Hour – registration here.

On 31 October, the grand gala, the thing itself – Arweave in Lisbon Demo Day, an entire day that will feature Arweave projects like Bundlr, Akord, RedStone, EverVision, Kyve, MetaWeave, and – registration here.

On 5 November, An evening of Decentralised Infrastructure featuring Kyve, Bundlr, and Akord – registration here.

Of course, Arweave News will be there to cover all the week’s highlights. The only question remains if we’ll meet you there as well. Remember, if you are a project that wants to build on Arweave, we’ll be more than happy to hear your story and have you for an interview.

ArDrive Team rebrands in AR.IO Team

From the beginning of the current year, it was apparent to the entire community that ArDrive team somehow outgrew ArDrive dApp. They branched into multiple protocols and dApps, so they decided to get things straight: ArDrive Team becomes AR.IO, while ArDrive becomes the flagship dApp under a much broader umbrella. Go and check our dedicated article for more about this rebrand.

Akord enables large file uploads

Sometimes the size counts, and Akord acknowledged that by allowing uploads on Arweave up to 30GB.

The Arweave network itself only enforces a 2^256 byte TX size limit, but the apps on top sometimes enforce lower limits for reasons of practicality. Great to see these being lifted!

No matter how hard we tried, we couldn’t have described this news better than Sam did.

Permaswap testnet is live

The long-awaited Arweave-based DEX is almost ready for business. Permaswap testnet is finally live. We know that EverVision’s community was more than eager to see it running, so now it’s the moment for everyone to get involved and test it to the breaking point. The more the testnet will be stressed, the better because now is the moment to catch all the potential bugs or glitches in order to have a flawless experience when the mainnet goes live. Also, there are incentives for those who help the Permaswap team in conducting a rigorous test set.

As you can see, in three days, over 3000 users joined the testnet, so the demand for an Arweave native DEX is more than confirmed.


Ocean Protocol awarded a 10k $ grant for Arweave integration

We signaled some time ago that Ocean Protocol is offering a grant for being integrated with Arweave. This week they announced the winner of that grant. will be the company responsible for the implementation.

Given the business model of the Ocean Protocol, which puts data at the core of its proposition, we only wonder why they didn’t start early to utilise Arweave’s permanent storage as a way to boost the perpetuity of their data sets.


A new tool for “fortifying” NFT collection via Arweave

Behold, a new player in the NFT storage arena just showed up. Meet Fortify, a project that will help NFT projects to switch the storage of entire collections to Arweave with just a few clicks. For now, they are compatible with Ethereum, Polygon, and Tezos NFTs, a selection that arguably covers the most active chains when it comes to NFTs. Given the relatively short development period, they did a nice job, so let’s give them a nice start by following Fortify on socials and sharing what they were up to. We are more than confident that a lot of NFT projects are in need of their tool and are unaware of its existence.

III. Things you won’t encounter on Arweave

We wrote about this practice at least a couple of times in this section. Still, the phenomenon is so widespread and entrenched in Web2 that it is somehow almost normalised.  That’s why we have to remind people every time we can that this is not normal. Deleting inactive accounts and related data is not cool.

Sam Wiliams, the founder of Arweave, again gave us a gentle nudge in not forgetting this very thing and pointed to the sole solution that will render this Web2 “feature” obsolete: building on Arweave.

By transforming the recurrent cost of storage into a single payment, Arweave releases an immense burden from the shoulders of web builders.


Join our

Telegram /Discord /Twitter

Leave A Reply

Your email address will not be published.