Personally I’d like some more detail on the potential pros and cons on these * to aid in forming an opinion one way or the other.
Also provisionally how is the Firo tokenomics structure going to work exactly within Avalanche, and the airdrops?
Tbh, I was hoping once Spark was released it would allow us to settle for quite a long time on a stable base protocol and to divert resources into building out Elysium and peripheral infrastructure so people have both easier access and reason to use Firo. For instance we’ve only just got a mobile wallet, which is pretty late in Firo’s development lifecycle.
Is it me, or is anyone else thinking we will see thousands of nodes just liquidate in order to stake AVAX (or some other coin) and earn passive income instead. Not sure how an airdrop can fix that… except for encouraging people not to do it before the chain switch. However I don’t know much about this whole proposal, so more detail is required for me personally…
Released v14.10.0 for with block time reduction and change in tokenomics. Have informed mining pool and exchanges and all major ones have confirmed support. We are recommending exchanges to pause deposits/withdrawals for a day after hard fork to ensure smooth transition and security.
fixed remaining Elysium issues before going on leave. Would require testing.
Worked with Dan to find workaround to Firo-Client build issues
Worked on Spark state implementation and would be able to push code soon.
Finalized and pushed mint creation and database code. Have been cleaning up.
Try to finalize Spark state main functionality
Tor upgrade to version 0.4.7.7
Finalize Tor upgrade and create PR
To look at high DPI scaling issue on QT wallet; 125% and above
Double checked faster block PR that works now flawlessly along with relevant unit tests
Peter did preliminary review of Levon’s first iteration of Spark integration PR , review still in progress.
Levon almost finalized Spark state, implemented wallet transaction scanning code and improved looks for Lelantus.
2nd integration PR to be finalized soon
Levon to start working on Spend transaction creation and verification. Test units will be implemented soon after. Verification of Spark Mints is done but not yet for Spark Spends
The 1st version of initial bare spark code will be ready in about a month.
Peter added additional testing for faster-blocks PR. Local mainnet testing is being done
Hardfork is still on schedule on the 16th June 12:00 UTC 2022
Peter dealt with quorum issues. A node provider updated their nodes by syncing one node and duplicating the blockchain to the rest of the nods. In doing so, causing individual masternodes’s secret to be invalidated causing chainlocks/instantsend to stop.
Zorayr is currently waiting for iOS developer account for iOS app to be publish on the App store.
Masternode collateral locking for mobile to be added.
Peter and the support staff oversee the Hardfork transition. The transition was flawless.
Explorer UI display issue (will be fixed)
Hardfork changed total supply value (decreased) and needs to be adjusted
Hardfork block is now known, therefore date for next halving needs to be set, team have roughly 1-2 years to adjust this due to faster block times…
LLMQ intervals can be included in the fix. LLMQ parameters might be adjusted to 2.5 minutes instead of 5 minutes (now similar as DASH). (Will require testing)
Levon is trying to move Spark integration code into one directory suggested by peter for ease of maintenance.
Spark state code bug has been fixed and cleaned up. Will try to finalize state code with spend stuff.
Unit test has begun implemented for mint creation and verification.
Peter cleaned up code and added missing stuff to make sure builds are running without crashing. Features will be added once builds are stable and works in desired way
Gevorg worked on Firo Masternode tool repository and implemented the Ledger fix commit from Dash Masternode Tool. Getting familiar with Electrum-Firo codebase and working on fx rate crash. Will try to finalize fix fx rate crash
Vong worked on adding RAP addresses to the address book in the Send page of Rich GUI Client. Will be fixing connection bug and add Send transaction completion for RAP addresses.
Masternode Onion addressing
To look at Onion address for masternodes.
Issues for onion address: Downtimes are frequent which will result in masternode being banned often