From Will Birks, Founder and Core Contributor, Amasa
While unpredictable and destabilising events beset the web3 industry and market, Amasa Labs stays focused on building. Since our last broad development update in September we have been sharing regular progress with the community via short dev updates on social channels. We will continue to do this, while also dropping larger reports on progress like this one periodically.
We’ve hit a couple of big milestones with the Amasa dapp recently. One is our deployment to Polygon mainnet, which we’re quietly very pumped about, but since this was just a necessary step along the path to onboarding users and not a full launch deployment, we kept it low key. What we’re building is pretty unique, and a lot of the data and metrics we needed to tune in the platform could not be properly tested on Mumbai testnet, so we’re now into a phase of testing and building in closed production.
We deployed V1.0 to mainnet, and are working on V1.1 right now, with added features and optimisations. Our findings post-deployment (overwhelmingly positive but with some technical challenges) have helped guide a revised MVP delivery schedule, now aiming to onboard our first external user group for closed tests in January.
I’m also proud to include here a milestone we announced last month, the launch of web3earner.com. This was created in line with our goals of growing awareness and accessibility of earning on web3, which we see as key drivers of adoption of web3. We will continue to add value for users of web3earner — including full web3 connectivity — while building the Amasa app. As projects integrate with Amasa to pay their users directly to Amasa accounts, they will be added to an in-app discovery dashboard feature which will also be connected externally to web3earner.
Compiled below is a condensed version of regular progress updates shared on Amasa social channels, as a summary of what has been in the works since our early September update.
September summary
- Ongoing testing on Mumbai Polygon testnet.
- Planning out Polygon mainnet deployment
- Completed UI design of V1.1.0 features including : User dashboard transaction history page / Amplify Product options info main page / Web3 income stream finder main page
- Working on Amplify Product options detail pages
- Deployed new version of smart contract to Mumbai testnet
- Evaluated back end transaction history storage; custom or API
- Updated/ completed documentation for internal new user testing
- Planning staging environment approach
- Regression testing on some V1.1 features
- Refactored products detail page component
- Completed “Network not supported” feature
- Worked on front-end configs to integrate new proxy contract branch
- Updated dev documentation
- Internal MVP user testing sessions with core contributors
- Setup Moralis API to test data storage transaction
- Worked on front end UI for W3IPs to complete MVP payIncome function to multiple users more accurately and easily (automatic balancing, CSV upload capability)
- Completed BDD test checking and troubleshooting
- Worked on script against re-entry attack
- Fixed / merged minor UI issues flagged in user testing
- Worked on code changes for issues flagged in user testing
- Security reviews and risk assessment test scripts
- Review of multi-sig implementation into fee vault and upgrade approvals
- Worked on Moralis API integration for transactions
- Setup Gnosis Safe multi-sigs for fee vault and upgrade approvals
- Continued working on payIncome UI
- Continued working on environment setup of payIncome page UI components
- Fixed Circle-CI issues
October summary
- Fixed / merged minor UI issues flagged in user testing
- Worked on code changes for issues flagged in user testing
- Completed BDD test checking and troubleshooting
- Integrated multi-sig on fee vault and contract activity
- Planning work on Polygon mainnet deployment
- Security reviews and risk assessment test scripts
- Proxy branch created for 1.1 features dev
- Worked on front end UI for payIncome feature
- Setup Moralis API data history integration
- Worked on Amplify Products detail info pages
- Regression tested next stage MVP features
- Worked on script against re-entry attack
- Planning staging environment approach
- Devops prep for Polygon mainnet deployment
- Worked on CI/CD pipeline / production environment
- Setup Gnosis Safe multi-sigs
Worked on V1.1.0 user features:
- payIncome UI design
- payIncome front end build
- User deposits feature UI design
- User transaction history page
- Amplify info page
- Web3 income finder page
November summary
- External review of smart contracts
- External review feedback implementation
- Mainnet deployment schedule
- Contracts successfully deployed to Polygon mainnet for further closed testing
- Unit and integration tests
- Additional Infura-based tests
- Mainnet contract function and user flow testing
- Smoke testing
- Full flow and components gas fee assessments
- Evaluation, spikes into gas fees and block gas limits
Progress on V1.1.0 user feature contract/back/front end:
- web3 provider finder page
- Transactions page
- Product info pages
December summary (ongoing)
- Gas cost optimisation & reduction
- Block gas limit optimisation
- Ongoing testing & bug fixing
Progress on V1.1.0 features:
- payIncome front end
- User deposit front end
- Addition of Aave yield-bearing pool integration
- User withdrawals option into MATIC from all Amplify options for easy rebalancing
- payIncome block segmenting
- Rewards distribution models
- Dashboard user data feeds
- Product info pages
- Updated copy and messaging across UI
Current build and project goals
Our main ongoing priorities for current build and project goals are as follows:
- Getting to beta user cohort testing stages in January with V1.1
- Naming conventions approach has changed from categorising DeFi options (Conservative, Moderate, Aggressive) to clearly listing the actual options available
- Our beta version Amplify options will not go through a community-vote process for selection but future versions will once beta has been fully tested and our model is more developed
- Governance model related to selections and other areas still a priority, still assessing optimal suite of of tools and step actions along full decentralization path
- Amplify options for beta will reflect market conditions, outlook and liquidity levels
- Key technical challenges are gas limit optimisation to enable scalable bulk paying of users from integrated web3 income provider platforms
- While we work to onboard web3 income providers to integrate, we will start our beta testing with a user-deposit feature, so aggregation and transfer of earned funds will be manual from users for beta (and will remain available in all future versions )
- web3earner will evolve from a discovery and educational platform to enable login with non custodial wallets, offering a range of web3 features and benefits for community and to web3 income providing platforms
— — —
Overall we continue to be prudent and steady with our build runway, in line with best practice and ongoing guidance from key advisors. Good things take time, and we are grateful for the patience of our community, partners and backers.
Market conditions are temporary, but earning on web3, providing value to networks and optimising value from web3 networks is in a constant state of growth and improvement. We remain committed to our goal of making that potential value more easily accessible.
Thank you again to everyone who supports us in these aims.
Will Birks, Founder and Core Contributor, Amasa
