Our Platform team has run a two-week hackathon in Tbilisi, Georgia. We gathered together to work as effectively as we can, solve problems, and leverage synchronous work.
Here's what we achieved.
TenderDash
Goals: Same block execution
What We Planned
- Implement same-block execution in progress
- First pre-release of same-block execution for integration (“alpha” quality) Done
- P2P investigating the issue mentioned in the post as the reason v0.35/v0.36 was discontinued in progress
- Backport remaining code from Tendermint 0.36 (master) Done
What’s Next
- Stabilization of same-block execution
- Investigate P2P issues
GroveDB
Goals: Fee continuation
GroveDB tasks
Features
- Sum Trees in progress
- Storage Flag system in review
- Plugged into RS-Drive
- Costs in progress
- Inserts previously done
Updates
- Just In time updates in review
- Dealing with returning values todo
- Deletes _in review _(probably needs more work)
- Batches in review
Storage Flags
5 types of Storage flags :
- Owned Single Epoch
- Owned Multi Epoch
- Single Epoch
- Multi Epoch
- None
Update Scenarios
When an item is updated:
- Same Size: No change in bytes
- Bigger: Might add another epoch and bytes for that epoch, or bytes to the current epoch.
- Smaller: Using LIFO remove bytes from last epochs.
Then we return all bytes added (this is known to be for the current user making the transition). We also return all bytes removed for each owner ID and the epoch.
GroveDB Update
Problem: When we add a non root value the parent will be modified.
Solution: Client must pay for their ONE parent reference that is not in their node.
What’s Next
- Costs and Worst Case Costs
- Continue plugging in our system to RS-Drive
- Delete and Updates making things smaller need to remove costs from epochs
- These returned costs need to be given back to users
SDK
Goals: Rework chain synchronization process (SPV)
SDK tasks
Reworking chain synchronization process
- Adapted new logic to existing tests and workflows with platform done done
- Intermediary QA and peer review done
- Unit tests done
- Integration tests done
Tests covering wallet-lib and dapi-client packages
What’s Next
- Testing with platform on testnet
- Consensus rules fine tuning for different networks
- Reorgs
Protocol
Goals: BLS rust bindings
Protocol tasks
- Add withdrawal to withdrawal queues in RS Drive in progress
- Rust binding for bls signatures library in progress
- Core 18.0.1 compatibility issue fixes in Insight done
- Platform update to Core 18.1.0-alpha.2 done
- Multi transaction support in Drive in progress
HTTPS for DAPI
- Move SSL commands to monorepo and make them work with Envoy done
- Make dashmate setup to obtain certificate done
- Enable SSL for DAPI client done
- Implement helper container which will renew certificate automatically in progress
What’s Next
- Continue on fee system
- Continue work on withdrawals
- Continue work on BLS Rust Bindings
- Continue work on HTTPS for DAPI
- Same Block Execution integration
- Release Platform v0.23
Rust Port Update
What we planned
- Bring all changes from v23 into the Rust DPP port in progress
- Make previous JS DPP tests work with Rust DPP binding in progress
- Integrate Rust DPP into SDK, Drive, DAPI and test suite in progress
More detailed progress report
- Porting v23 changes: Previously we’ve finished 10/20, current state is 16/20
- Rust DPP integration: WASM build and bindings are created, smaller data structures are integrated and tested: We’ve added a CI, made some other data structures worked, eliminated bugs and adjusted interface to match existing usages in the platform codebase
Core Update
v18 status & BLS upgrade
v18 Hard fork status
LLMQ_60_75 quorums, isdlocksBLS upgrade
Basic BLS schemeNext releases
v18.1 - Next week
Asset lock
Implement new special transactions: Asset Lock and Asset Unlocks (withdrawal) done
Implement Credit Pool in progress
Unit tests done
Functional tests in progress
iOS Update
Quorum Rotation work
Fix: Core v0.18 Issues done
Write tests for verifying quorum rotation members done
Dashwallet iOS Front End
Coinbase integration in progress
Fixed an issue when when the app locks randomly
Redesigned Navigation Flow of Settings screen
Should Platform be run on all nodes?🤔
Masternode Solution
- Higher Fees
- IBC more work
- Less Chance of Double Sign Attack
- Lower TPS
- More Decentralized VS
High Performance Masternode Solution
- Lower Fees
- IBC less work
- Very little chance of a double sign
- Higher TPS
- Less Decentralized
Top comments (0)