A quick update on how we calculate dev activity: To create these reports, we are in communication with some of the most active projects on the Ethereum network. In turn, it’s become increasingly clear to us that tracking only the project’s main github organization – as some sites showing github dapp activity do – is increasingly deficient.
A github organization consists of a number of repositories, which is where each project’s source code is stored. For example, Santiment’s github organization is https://github.com/santiment.
While most code is nested inside the project’s main organization, there’s a growing number of instances where the full scope of a project’s development work is dispersed across several github orgs, all belonging to and populated by the same project.
This means that a relatively significant portion of a project’s monthly code output (stored in complementary or side organizations) can – and sometimes will – be unaccounted for.
To make our dev activity calculations more reliable, we’ve recently extended the amount of github organizations that we’re able to track per project. We’ll also work with the projects to add any auxiliary organizations to our database, and provide a more comprehensive view of the actual development work done in crypto. Enjoy the article!
Each month, we shine a spotlight on the 10 ERC-20 projects with the highest-recorded developer activity for the past 30 days, as calculated by Santiment.
Development Activity is an oft-underrated indicator of project success, as it demonstrates the month-to-month commitment to creating a working product, continuously polishing and upgrading its features, and staying true to the long-term roadmap.
In this report, we are focusing only on ‘pure ERC-20’, i.e. those projects that are (currently) committed to developing on Ethereum, and have as of yet no working mainnet or an imminent token swap.
You can check out the latest dev activity ‘power rankings’ for all ERC-20 assets on SANbase, by filtering the ERC-20 projects by Dev Activity (30d).
As always, we asked all of June’s top 10 most active ERC-20 dapps what they’ve been working on for the past month. Here’s what they told us:
“The Storj Labs team has continued to make strong progress towards its production launch this fall. The team just released its Beacon release. Its Pioneer release, which is the first phase of its Beta, is coming soon.
As part of its Beacon release, the team finished its macaroon implementation. This means clients are able to share encrypted files stored on the network with others. Beacon also added general performance improvements.
Storj added IP filtering so that one particular storage node doesn’t get an uneven distribution of file pieces, keeping data stored on the network amply distributed. The reputation model was also refined to better determine which nodes should be disqualified from the network. Storage node containment was also added, giving storage nodes multiple opportunities to respond to Satellite audit requests in case they happen to go offline right at the time of the request.
During June, Storj also released its C library bindings for libuplink. They added the ability to determine how much storage and bandwidth is attributed to the network through its Open Source Partner Program members. These open source companies and projects earn revenue when their users store data on Storj.
Storj also holds quarterly town halls, with the next one happening on July 10.”
“A look back at the last month of activity at Status. The team has been working to prepare the app for code freeze and the upcoming security audit. Priority items include:
- Multi-account support including foundation for multi-account UI within the wallet.
- Improved onboarding
- New Profile UI and ENS integration
- App performance improvements: partition topic and topic negotiation is currently in testing. Currently working on moving protocol to status-go which is a huge piece of work. More App modules including network, extensions, and goog.i18n. Faster rendering of formatted text and upgraded react-navigation
- Keycard team has been making great progress with the Status integration while the Keycard App for Ledger Nano X is ready.
- Continued progress on SNT use cases, features, and swarms including Teller Network, DApp Store, Sticker Market, Topic Democracy
- Messaging protocol research – minimum viable data sync paper complete, mvds remote log extension, and swarm adaptive nodes in progress with Swarm team.
The most recent releases of the Gnosis Safe mobile apps feature a more streamlined Safe creation process as well as the new, formally verified v1.0.0 Gnosis Safe smart contracts. There are also new fee payment options. Safe mobile users can now use ETH as well as a number of ERC20 tokens (e.g. DAI and OWL) to pay for Ethereum transaction fees and the Safe creation fee.
The Safe team is currently adding support for several Safe management functions such as adding and removing wallet owners. These features will be part of an upcoming release called the Gnosis Safe for Teams. Gnosis is in the process of conducting user tests on the existing prototype. If you are interested in participating, please reach out via Telegram or Twitter.”
“The month of June for MESG was focused on finalizing the foundation for the implementation of the decentralized network and the workflow engine, the next two major features.
We released new versions of the Engine and the JS library and introduced a new CLI. The Engine and the JS library are now implementing the simplification of Service tasks’ outputs proposal. We replaced the previous CLI written in Go by a new one written in JS. You can learn more about these releases by reading the Release Notes.
We are currently working on finalizing and cleaning the foundation of the next features.
- Service compilation
- Instance Database
- Chain of Executions
- Reorganizing the SDK package
- Standardisation of the gRPC APIs
- Implementation proposal of CosmosSDK
- Specification proposal of Workflow Engine
Check out the latest product roadmap to get more details.
We also brought more transparency to the Algorithmic Token Distribution by upgrading its Dashboard. This system is releasing progressively the MESG Tokens to increase stability and transparency. To learn more about the ATD, check out our Handbook.
And finally, we are officially part of the OmiseGO Developer Program! We are building a Plasma watcher that automatically exits the plasma chain if there is any issue and challenges invalid exits. The watch is composed of a MESG Service and an application.”
“Augur v2 Development work is progressing at a very good clip, and the Augur dev team is focusing nearly all of our efforts on completing the first level of integration with the v2 contracts.
On the high level the team is working toward a major internal release called
v2.0b containing existing redesign pages, followed by
v2.0c containing new market creation flows. After these major milestones have been achieved, smaller bi-weekly internal milestones will be established building up to V2 launch.
- Contract changes have been put in place to address various issues from the first round of Audit feedback from Zeppelin. (https://github.com/
- The v2 UI can now run entirely in the browser, and the last vestiges of Augur Node are just being removed.
- The Backend and UI teams are collaborating to shore up the new API layer (https://github.com/
AugurProject/augur/tree/ master/packages/augur-api) so that it supports all necessary data for, the Trading, Account, and Portfolio pages.
- The UI team has done considerable refactoring, removing a lot of compatability code from the UI and moving business logic and type transformations into the API layer.
- The UI team began splitting up work, with half the team focusing on the next internal release
v2.0b(Trading, Account, Portfolio), while the other half of the team has begun work developing on the brand new market creation flow due in
- The team is preparing to spin up a new public testnet endpoint for the V2 UI. They will attempt to deploy this UI along with the current V2 contracts to Rinkeby for development purposes early this week. This will sit alongside the current https://dev.augur.net site.
- At the same time, a v1 UI release containing improvements to the recently release Liquidity & Spread Filter is in the works.
“Golem has had a really busy June. Our development activity increased on every front. Last week we revealed the new marketplace model that will be integrated in 0.20.0 – because the WASM and RASPA usecases that come with this release need a better marketplace model. However, this is not the only model that Golem will have. In the future people will be able to pick from different approaches, and usecases.
We are very excited about gWASM. Why? gWasm is our new use-case AND a core part of the Golem API, and developers can already build their Golem integrations through it. As the Golem API/Task API development progresses, both gWasm and the API will get better.
0.20.0 is now getting its final tweaks while the company – Golem – is undergoing exciting changes, and the second half of 2019 will show how hard we are working”
7. POA Network
“A lot has been happening recently within POA Network and out development activity is very much evident of that. To start it off, we have started implementation of POSDAO consensus and the implementation of HBBFT into xDai Chain and POA Core networks. POSDAO introduces delegated proof of stake into our networks and is a new consensus that we have been developing over the last 8 months. You can read more about it on the whitepaper here
BlockScout has also had a big month with a major release of version 2.0.0. This release The BlockScout 2.0 update is a big release that is made up of over 20 new features and enhancements and over 35 bug fixes and patches. The new enhancements deployed with BlockScout 2.0 include: major Facelift and theming capabilities, verifying transactions through other explorers and the integration of our staking application. You can check out the full details of the release here.
In regards to our interoperability protocol, we have been working on implementing a version of the TokenBridge that will be used as bridge between Ethereum and Binance Chain. The spec and discussion for that can be found here.”
8. Loom Network
“The Loom team has been as busy and productive as ever this past month! Here are some highlights of what we’ve been shipping:
- Launched TRON + PlasmaChain integration. Now users can send TRX and native TRON-based assets between Loom and TRON mainnet.
- Released Loom Wallet, which allows users to display Loom PlasmaChain assets, send/receive transactions, deposit/withdraw to Ethereum + major chains (soon), and sign in with MetaMask.
- Released Loom 2.0, Build 1085 – focused on mainnet builds, so this has a large backlog of features for third-party chains. Major updates for Performance, Caching and DPoS.
Integrated and launched on DappRadar: https://dappradar.c
- Rolled out support for Universal Transaction Signing with Portis and Fortmatic.
- “The Smart Contracts team has been hard at work testing adapters for the different collateral tokens that may go into the first release of Multi-collateral Dai
- Work has ramped up on Oracles v2
- We’re preparing for another round of Formal Verification on peripheral smart contracts for MCD”
Proposals or ZEIPs , encompassing pretty much the entirety of the 3.0 feature set. They were presented to the community during the Dev Meeting on May 7. Proposals include some pretty big changes: property based orders, a KyberAssetProxy, and changes to the protocol fee structure, to name a few.
Launch Kit Updates – We released an update to our off-the-shelf relayer starter kit. Back in November, we released Launch Kit, an example back-end component for a 0x relayer, a Node.js server that hosts an orderbook behind our Standard Relayer API interface. Last month, we added a pair of beautiful React front-ends, so you can quickly spin up a whole end-to-end application to offer traders either an interactive order book full of your favorite tokens or a shiny marketplace for your favorite NFTs. See all the details in our recent blog post, Launch Kit Reloaded.
In May, we made some exciting advancements towards this language-agnostic vision. As a first step, we integrated with ethereumjs-vm in order to execute purely off-chain Solidity functionality within a Node.js process. With this, any calls made through our generated wrappers to a pure Solidity function will use a simulated EVM instead of an eth_call. This will allow us to deprecate utility code that previously had multiple implementations in different languages. Separately, we’ve begun modifying our abi-gen utility, which can generate TypeScript wrappers for any Solidity contract, to also support Python (in addition to TypeScript). Watch for releases of this functionality in the coming months.
Other exciting things happening in the 0x ecosystem: