📣Weekly Build Update @everyone

Our focus this week has been optimizing and enhancing various aspects of the vNode system to prepare for shipping, including performance improvements, stability fixes, codebase cleanliness, and user accessibility.

vNode #001 is headed to Taylor this weekend for review, that is the final green light before the first full batch is cleared to ship!

In addition, our Marketplace is coming along and nearly ready for rollout.

Part 1 of 2

Part 2 or 2

Here is a list of accomplishments from the past week and a peak behind what is our focus for next:

This Week’s Achievements:
✅Optimized vNode-updater RPC calls via Infura to ensure we stay within limits and maximize efficiency.
✅Successfully deployed a fix to the testnet vNode build, enhancing its stability and performance.
✅Conducted a fix and refactor of NAC origin check, streamlining processes for better functionality.
✅Addressed various in-code TODOs, ensuring a cleaner, more efficient codebase.
✅Resolved benchmark issues, optimizing performance for smoother operations.
✅Thoroughly documented Democracy and treasury flow with comprehensive diagrams.
✅Implemented Deeplinks for both platforms, enhancing user accessibility and navigation.
✅Expanded test coverage for the marketplace, ensuring robustness and reliability.
✅Rectified the indexer on the development environment using Explorer, boosting development speed.
✅Introduced search functionality for internal transactions, aiding in data accessibility and analysis.
✅Conducted extensive research on new providers to replace Infura for improved services.
✅Swiftly adapted the codebase to accommodate the transition to the new provider seamlessly.
✅Updated the vNode ISO to disable UPnP after shutdown, ensuring security and stability.
✅Resolved issues related to port forwarding, ensuring seamless connectivity.
✅Successfully deployed FE with deeplinks, improving user experience.
✅Initiated Cloudflare API calls for whitelabel DNS names, enhancing customization options.

Upcoming Plans:
🟡Implement a comprehensive vNode package update for enhanced functionality.
🟡Develop a detailed plan for Energy broker and democracy augmentations implementation.
🟡Implement an energy fee split burn/recycle mechanism for sustainability.
🟡Address and resolve any remaining benchmark issues for optimized performance.
🟡Roll out the 'Become a Validator' flow for seamless user integration.
🟡Focus on Marketplace improvements and bug fixes for a smoother user experience.

📣 Build Update

We have a vNode ship date!

Drew is getting the final build instructions this weekend to review and approve for TD Synnex. Once reviewed and approved, they will start building and shipping units as they are completed. Since the US has a work holiday on Monday, we expect emails containing shipping information and tracking numbers for end users starting no later than Monday the 22nd.

Additionally, Operator Welcome emails will go out next week with full orientation instructions and invites to our vNode Operator/Operations server.

Regarding Dev work on the various products, below are the technical accomplishments from this past week along with the work planned ahead of us, per usual:

*VTRS PowerPlant DAO*
Achievements:
✅ Fixed bugs from the community during the presale and claim process in Open Beta stages.
✅ Updated the explorer after changes in the internal transactions and the presale for testing on the Arbitrum.
✅ Modified logic in GraphQL subscriptions for stake/unstake.
✅ Added a couple of fields to the entity returned to the frontend
✅ Fixed logic at the application start (for restarting in case of server crashes).
✅ Fixed reputation values and last/first transactions on the address page.
✅ Added these changes to the frontend.
✅ Enhanced functionality for adding statuses to internal transactions.
✅ Switched from Sepolia to Arbitrum in the development environment
✅ Deploy Stagenet nodes
✅ Deploy Stagenet explorer app FE and BE
✅ Deploy marketplace FE
✅ Set up monitoring for webapps
✅ Load and performance testing
✅ Democracy documentation
✅ Treasury documentation
✅ Benchmarks fix (system overall)
✅ Energy fee split burn/recycle mechanism
✅ Energy broker implementation research
✅ Become a validator flow

Plans:
🟨 Presale bug fixes
🟨 Marketplace release
🟨 Faucet improvements for gaining Arbitrum tokens
🟨 Terraform code for AWS
🟨 Governance
______________

*COMPLiQ*
Achievements:
✅ High Level scope approved
✅ Prototypes designing
✅ Freeze vitreus-one code base and save locally/remotely for processing with Blockchain
✅ Working on crc-check feature for datastorage-gateway

Plans:
🟨 Designs
🟨 Development of Frontend and Backend
_______________

*Vitreus CyberVision*
Achievements:
✅ Preparation for the CyberVision presentation for SME - meetings with PO, finalizing the project description doc to be used in the presentation, meeting with the designer to choose the designs, clickable designs creation
✅ Updating user stories after specifying new requirements by PO. Publishing them on consideration in the client's Confluence (cybersecurity events, cybersecurity incidents, assigning confidential status to incidents)
✅ Updating prototypes  after specifying new requirements by PO
✅ Blockchain transactions' triggers (user actions and event-incident states) definition 
✅ Summary - 10 user stories are under review now, 14 are approved, 3 are in progress
✅ logs and alerts integration with Synthetic data source
✅ Real data uploaded into log source

Plans:
🟨 User Stories creating
🟨 Prototyping
🟨 UI/UX
🟨 Integration testing for Log Source

We. Are. Vitreus.
LETS GOO!! 🫡🚂

📣 Build Update

Focus is turning towards preparing for Stage 3 beta testing. We’ll have 150+ vNodes coming online over the next few weeks.
- vNodes (being shipped)
- Marketplace (finished and deployed to update)
- vGovern (finishing development)

vNode Operator welcome emails have gone out and we will be working to set operators up in their Operations channel over the next few weeks while the vNodes come online.

Technicals update below 👇🏼👇🏼

Vitreus PowerPlant
Achievements:
✅ AWS processing
✅ Terraform for AWS and Vultr
✅ Deploy marketplace testnet apps
✅ Rewrote the logic for loading metadata to IPFS
✅ Connected a new service (Pinata)
✅ Tested and deployed to all environments
✅ Fixed logic for determining statuses for nodes
✅ Improved blockchain connection
✅ Become a validator flow improvements
✅ Various bug fixes and stabilisation for vApp
✅ Sign transactions for Marketplace
✅ Energy Broker Concentrated Liquidity Implementation
✅ Energy broker + staking + fees modeling
✅ Utility fee fix
✅ Devnet deploy fix
✅ Wallet connect code refactored
✅ Updated configurations on all frontends separated from the backend to ensure compatibility with older Apple products
✅ Network mobile connection to Marketplace

Plans:
🟨 Terraform code for AWS
Governance
🟨 Energy Broker Concentrated Liquidity Implementation
Energy broker + staking + fees modeling
🟨 Implement deep linking for transaction signatures on the marketplace

______________
Vitreus CompliQ
Achievements:
✅ Initialized the repository
✅ Wrote basic configurations for Backend
✅ Implemented user and role modules (started the authorization module)
✅ Wrote Docker Compose and Dockerfile for server deployment
✅ Layout for 3 out of 4 screens
✅ Deployed Backend on the server

Plans:
🟨 Layout finalization
🟨 API for blockchain-FE communication
🟨 Deploy CompliQ FE
🟨 Deploy CompliQ nodes

_________________
Vitreus CyberVision
Achievements:
✅ Integration of the Elastic into OPENCTI (connectors added, configured, in testing)
✅ Real data load in progress
✅ Backlog updating according to new requirements
✅ Existing user stories and prototypes updating (incident assessment, materiality assessment, general view of all events in the System, general view of all incidents), publishing new versions into the confluence
✅ New user stories and prototypes designing (view events' details, investigation forms, take control of security events, register incidents based on the event, close security events)

Plans:
🟨 Automate existing elastic instance to send required alerts into Data Source 1
🟨 Blocker with splunk still under investigation
🟨 Integration testing for Data Source 2
🟨 Finalize all user stories related to the security events  
🟨 Continue developing and updating the user stories related to the incidents section
🟨 Meeting with PO to discuss user's activities at the stages of incident refinement and incident remediation

📣 vNodes SHIPPING !!!

vNodes began shipping yesterday. We had 3 units go out with more expected each day from here on out. I’m not sure what cadence they’ll be assembling at, but we should get a feel for it over the next few days.

Again, the vNodes will be assembled and shipped in the order they were ordered online for ALL units that have been ordered. Shipping occurs immediately once assembled and tested.

Keep on the lookout for that shipment tracking email and let the community know when you receive it!!

It’s happening! We are here to deliver.

We. Are. Vitreus.
LETS GO!!! 🫡🚂

📣 POWER PLANT BUILD UPDATE

⚠️ 34 MORE VNODES SHIPPED TODAY!!!

While everything is flowing now on shipping and bringing 165+ vNode operators online, we want to keep other important initiatives in mind as well… namely vGovern, our onchain decentralized governance platform for managing the affairs of the DAO.

Attached you’ll find a screenshot of the vGovern platform for web. While the UI design could still change in some aspects, what you see is a strong visual understanding of what the Web app will look like. Finishing this vGovern platform is top priority over next couple weeks while we tweak the vNode network and transition into testing the staking.

For the more technically savvy…

Power Plant Achievements:
✅ Stop being a Validator Flow
✅ Stop request being a Validator Flow
✅ Deeplinks for Marketplace
✅ Liquidity provision for energy broker impl
✅ Energy broker swap feature partial impl
✅ Slashing issue research
✅ Improved the request for obtaining stakes for validators
✅ Fixed a bug related to displaying reputation
✅ Added new fields for data sent to the frontend
✅ Fixed the handler for the validator activating event
✅ Adjusted calculations for stakes
✅ Fixed the mint request on the blockchain
✅ Switched the network on the testnet to Arbitrum Sepolia
✅ Implemented logic for reconnecting the mobile app to the session
✅ Live updates on Marketplace
✅ Troubleshoot and redeploy testnet
✅ AWS
✅ Terraform
✅ Helm

Power Plant Plans:
🟨 Finalize swaps
🟨 Integrate energy broker into runtime
🟨 Fees-staking-swaps viability modelling 
🟨 Slashing issue fix
🟨 Update vNodes with the latest Power Plant version
🟨 AWS
🟨 Terraform
🟨 Helm

We. Are. VITREUS.
LETS GOO!! 🫡🚂

📣 INNOWISE + POWER PLANT DAO

As of today, we have reached an agreement with Innowise Group to join the VITREUS DAO as a builder/developer and assist in driving growth and maintenance of the VTRS ecosystem.

It’s incredible to see a large mature company like this take such deep ownership and care in the ecosystem they’ve been working so hard to build for Vitreus over the last 10 months. We are fortunate to be able to take this partnership to such new levels.

Innowise has agreed to a 2-year team token package that progressively vests alongside much of the rest of the team. In return, serving the DAO in the technical committee capacity with a select few open to serving on the council also. We are beginning with 10-12 developers on the dev team and will expand that as additional capacities and specialties are needed. Incredible scaling capabilities for the VTRS ecosystem.

This arrangement provides us with access to any and every area of speciality that we need to accommodate the development needs of the Power Plant DAO moving forward and into the future.

In addition to the development specialists, it also brings us a highly competent Project Manager and experienced Salesman to recruit other Web3 companies and projects to build on VITREUS’ Power Plant also.

This plays a CRITICAL role in the achievement of the DAO’s hyper-success objectives for VTRS and Power Plant. I am very happy with this redefined collaborative partnership.

Level UP!!

WE. ARE. VITREUS.
LETS GOO!! 🫡🚂

Build Update

Good day @everyone ,

A new vApp Update was just released today to the beta group encompassing the many bugs that have been uncovered during the last few weeks of testing. We certainly appreciate the community being so engaged and patient to keep this process moving.

Also, vNode shipping is back underway with overseas international shipping beginning mid next week. We are continuing to work through some bugs across the DePIN network. We have also pushed some updates to the 35 units already online.

Highlight of this last week brought the announcement of Innowise making the decision to partner with Vitreus DAO. We continue to look for opportunities to add integral partnerships to the DAO for the future.

Lastly, we have received the greenlight from Innowise on a plan to begin working on a DEX integration. More details to follow in the weeks ahead.

Vitreus PowerPlant Technical Details
Achievements:
Script for vNode updater
AWS+terraform+helm
Troubleshoot production vNodes
Deploy a fix to production vNodes
Troubleshoot and fix testnet DBs
Started a repository for governance
Set up a basic UI with navigation across pages and our Web Components
Pulled the list of extrinsics and their types
Reusing functionality from Polkadot Repository
Explorer improvements
Improved obtaining validators function for Marketplace
Added the capability to connect multiple mobile and frontend sockets to a session for Wallet
Slashing improvements on the chain
Improved Become a Validator flow
Improved mechanism of picking up a Validator

Plans:
Governance
Refining the logic on Compliq
Energy broker progression
Log out flow for vApp

We. Are. Vitreus.
LETS GO!!

📣 Build Update

As @everyone likely knows, we are deep into TestNet on the defi ecosytem in stage 3 of our testing. We still have a couple more features that we are waiting on from Innowise before we are ready. Please see below for a summary and estimated timeline that has been communicated to us by Innowise.

vNodes — 64 online, 121 shipped. 40 US units left to build (awaiting RAM). 8 international units left to build (awaiting RAM and power cords) — Target Date Feb 28, 2024

vGovern — Target Date February 29, 2024

VNRG/VIP/VIPP — Target Date March 15, 2024

Mainnet — Target Date March 31, 2024

Marketing — We will be using the DAO’s vGovern testing envirorment for the marketing proposal voting so we can get that through and engage with Coinbound ready to hit the marketing when Mainnet goes live.

Technical Tasks are as follows:
Vitreus DAO Achievements Last Week
● Deploy explorer infrastructure and DB on test account
● Set up ArgoCD
● Troubleshoot and fix NX issues
● Set up ECR and bitbucket pipe for new repository
● AWS+HELM+Pipelines
● Redeploy explorer FE to CF
● Completed all governance pages with the integration of
up-to-date information
● Initiated the layout for modals on the pages
● Explorer Backend moved the to a separate repository
● Refactored code and configured the backend for deployment
● Initialized the repository for vNode Manager
● Configured settings
● Integrated file storage
● Added endpoints for registration, login, and account reset
● Added an RPC endpoint for socket connection
● Wrote a basic socket module
● v3 factory wrapper implementation + tests
● v3 pool wrapper implementation
● v3 router wrapper implementation
● v3 position descriptor (part of dex) partial implementation
● v3 position manager (part of dex) partial implementation
● Log out flow for vApp
● Details for all the transaction types
● List of failed transactions
● Relaychain migration

Part 1 of 2

Vitreus DAO Plans Next Week
● AWS+HELM+Pipelines
● Set up ArgoCD
● Finishing the development of modals
● Handle different scenarios and refine validation
field logic for extrinsics
● Achieve a UI that is fully functional without the
necessity of capturing signatures from the mobile
side yet
● vNode Manager backend in progress
● Fix position descriptor
● Implement tests for router
● Finalize energy broker
● Full dex wrappers implementation
● Relaychain migration
● vApp KYC integration

📣 Modifications to KYC/Network Security Mechanisms

As everyone is aware, Vitreus DAO is a Decentralized Autonomous Organization (DAO) which has caused us to reevaluate the nature and elements of the ecosystem as we pursue DECENTRALIZATION in its purest form.

As part of the evaluation, we determined that the currently planned KYC elements of the ecosystem no longer fit within the DAO’s DNA and have made the decision to remove all requirements of KYC within the MVP build. No delays are expected at this time.

OLD
KYC used to be required for:
- Initial Claiming of VTRS
- Staking (delegator)
- Participating in Validation (operator)
- Sending VTRS (not receiving)

Minimum Bag Size for becoming an Operator
- 1 VTRS

Since the minimum bag size was so low, the KYC element served as our security mechanism to ensure against the possibility of Sybil Attacks of the network. This method has its shortfalls as KYC is becoming increasingly possible to fake.
___________________________________

NEW
1. NO KYC REQUIRED ANYWHERE WITHIN VITREUS DAO
2. vNode sales have been suspended until after MainNet launch. We will continue to honor free vNodes on a case-by-case basis for those who are close to accumulating the necessary qualifications.
3. Existing vNode owners (170) will clear KYC directly with Onfido (free of charge) outside of the ecosystem. We will send an email with instructions and link for completion, with added instructions on how to purge records from Onfido’s retention also.
4. Minimum Bag Size for becoming an Operator is 1,000,000 VTRS (DAO can modify this minimum as they see fit)
5. Anyone who has purchased a vNode as of today, will not have to satisfy a minimum bag size. They will be grandfathered in as a cleared validator/operator.

170 nodes is more than adequate to establish and grow the network. Additionally, the new minimum bag size is a more secure mechanism for preventing Sybil Attacks than the old KYC method. We are encouraged by this solution to take care of everyone who has already planned to become a validator. Once again, early believers have been valued and cared for.

WE. Are. Vitreus.
LETS GOO!! 🫡🚂

Build Update

The focus for this past week for the Innowise team has been fixing bugs, getting a new build update pushed to vApp/vNode, and transitioning from Vultr to AWS. This will help incredibly with reliability issues. They are continuing to work on the bug fixes that have been submitted by our amazing beta team.

vNodes: The assembly and shipping of vNodes has begun again with all parts and cords in inventory now. 18 units have gone out in the past two days and we should have ALL units shipped by the end of next week. As of the previous announcement, new vNode sales have been suspended and sales are planned to be reinstated on the launch of Mainnet.
Build Update
VGovern: The DAO governance platform has been completed and they are positioning it for some mock proposals for us to begin testing as a community in the next 2 weeks. We will begin with a proposal for the marketing campaign.

Slashing: Slashing has been confirmed to be 100% reputation based yet Innowise HIGHLY recommends we transition to token based slashing around 6 months after Mainnet deployment once the network is fully stabilized.

It was confirmed today that the Mainnet deployment targeted for Mar31 will consist of the Block Explorer, vNode network, vApp, VTRS, Staking, Marketplace, vGovern, and VNRG/Energy Broker.

Part 1 of 2

Part 2 of 2


Technical tasks listed below.
Achievements:
AWS+HELM+Pipelines
Redeployed Frontends
Deployed Governance
Completely refactored the code in the new backend repository for Explorer
Fixed database queries for Explorer
Improved error handling for Explorer
Fixed calculations for the claim amount
Added a new library for calculations of the claim amount 
Moved the backend of the Presale app to a new repository
Addressed and fixed certain deployment-related issues for the repositories deployed to AWS
Fixed position descriptor
Full DEX wrappers implementation
Treasury extension hotfix
Slashing improvement in progress
Governance libs refactoring
Implemented modals on all Governance pages
Made minor fixes on the marketplace, explorer, and web components.
vApp new build released
Merged frontier
Merged custom RPC
Merged benchmarks
Added parachains support to the runtime

Plans:
Custom vNode Backend progressing
Governance stabilization
Improving slashing
VIP/VIPP for vApp
Fix tests
Launch a test parachain and make sure it works with relay chain

We. Are. Vitreus.
LETS GOOO!!!
@everyone

Chad | Core | Vitreus — Yesterday at 9:15 AM
NO ETH GAS TO CLAIM SEED & PRESALE

To clarify, we will have a total of 3 NFT contracts for claiming purposes:
Seed NFTs
Presale NFTs
Mainnet NFTs (new)

We will END Presale NFT sales prior to Mainnet launch and take a “snapshot in time.” While we will stop the smart contract, transfers of NFTs will still be possible.

Seed and Presale NFT holders will be written into the genesis block on Vitreus Chain allowing these holders to claim WITHOUT having to pay ETH gas fees.

The receiver of mainnet sale proceeds will be the DAO treasury wallet on Ethereum. DAO will receive 100% of proceeds from Mainnet NFT sales.

Future Mainnet NFT holders WILL have to pay ETH gas to claim.

We. Are. Vitreus.
LETS GO!!
@everyone

📣 BUILD UPDATE

STILL ON TRACK FOR MARCH 31 MAINNET.

Claiming — *steps will be the following:*
1. connect ethereum wallet
2. connect vApp
3. initiate claiming
4. sign message on ethereum wallet (doesn't require gas)
5. approve transaction on vApp (gasless)

* see above for the “No Gas to claim” announcement

Staking
Immediately following the claiming of your VTRS, you will be able to proceed to the staking page and process your stake on vNode to begin accumulating your VNRG. Your VNRG no longer carries an expiration.

vGovern
Our DAO governance platform is being polished up and will be ready for some initial testing next week. We are also assembling an initial bundled proposal to fast track a referendum vote ASAP after Mainnet deployment so we can begin developing high priority items. The Vitreus operations wallet has been updated with 2 new community signors and 1 additional required signature to initiate a transaction. That makes 5 total signors and 3 required for each transaction. I am not a signor.

vApp
The final feature of vApp is the VNRG. This is being tested internally currently and will be pushed in the next update next week for testing. Additionally, we will be submitting all the final documents for Apple and Google app listing which we expect to take about 5 business days to approve.

vNodes
A back end update is expected to be pushed next week to the units in the field as well. Denis will announce this in the vNode Ops channel and will explain any procedures required.

Part 1 of 2

Part 2 of 2

*Technical Detail*
Last Week’s Achievements:
* VTRS tokenomics model
* VNRG tokenomics in progress
* Energy transfer in vApp
* Implemented versioning for the mobile application
* Developed a custom file storage for our custom backend
* Wrote logic for requests on the custom backend
* Refactored and fixed bugs on the custom backend
* Marketplace improvements
* Relaychain implementation
* Claiming fix in progress
* Authentication/recovery module, including storage and vulnerabilities fixes for the custom backend
* Extended logic to include login status and fetching Wi-Fi credentials to prevent the user from using default ones
* Added access for developers to EKS
* Added pgadmin to cluster, write configs
* AWS+Terraform+helm
* Troubleshoot vNodes with QA
* Check and deprecated unused VULTR resources
* Preparation before mainnet launch
* Start deploying testnet
* Сurator assignment flow on the bounty page for Governance

Next Week’s Plans:
* Finalize VNRG tokenomics
* Balance and transactions list for Energy Tab in the vApp
* Finalize the custom backend
* Marketplace improvements
* Integrate versioning on the mobile app with API key guard and validation
* Add an indexer to the explorer for events on the Backend
* Claiming fix
* Vesting
* Integrating and troubleshooting the custom Backend with the mobile app
* QA testing the custom Backend
* Deploy testnet apps
* Update vNode backend
* Rewrite the claiming process
* Adaptive layout for Governance

We. Are. Vitreus.

📣 BUILD UPDATE

This week’s focus has been all hands on deck polishing the VTRS claiming, vApp, vNodes, vGovern, and Explorer!

As Mainnet draws closer, we are drafting our transition roadmap for the community on what to expect over the coming month. We will share this “Road to Trading” communique with the community on Monday.

Mainnet remains on target for April 1

We have a very clear plan that has been coordinated with Innowise and also are beginning the briefings for the council as well.

*Below are the technicals tasks details*
Last Week’s Achievements:
- Bugfixes and improvements for vApp
- Released custom vNode Backend - vManager
- Fixed claiming on the Chain
- Vesting implementation
- Claiming genesis implementation
- Vesting genesis implementation
- Deploy AWS TestNet apps
- Deploy production frontends
- Implemented logic for fetching the version of vManager
- Added guards and validation for requests related to the mobile app version
- Changed the database table structure, which required some adjustments to the code logic
- Added an indexer for events from our network for Explorer
- Fixed the logic for inactive stake amount for Marketplace
- A button on the Marketplace to unstake all inactive stakes
- Energy tab for vApp is ready for QA
- Updated the claiming process, removed contract origin, and replaced transaction signing with message signing
- Updated the Web Components, prepared everything for production
- Optimized requests on the bounties page in Governance and fixed all requests for mobile compatibility
- VNRG tokenomics
- Implemented RPC endpoints for VNRG per stake currency and swap rate parameters
- Customizable constants

Next Week’s Plans:
- Launching the MainNet environment
- Version checks from vApp to vNode
- Change Wi-Fi credentials flow for vManager
- Vesting genesis implementation
- Deploy AWS production apps
- Integrate claiming with the updated network
- Customizable constants for tokenomics

We. Are. Vitreus.
LETS GO!! 🫡🚂
@everyone