- Craig
- 0.0.9.99-dev has been shared with the team for testing, report issues to: https://github.com/OmniLayer/omnicore/issues
- any major issues to discuss?
- TMSC consensus issue (raised by Sean): https://github.com/OmniLayer/omnicore/issues/134
- issue has been closed, as the consensus issue was to be expected, is now ignored
- we need a “foundation owned” P2SH address which the foundation can use to sign messages to activate features
- each foundation board member perhaps each has one key for the multisig (should Exodus be one of these?)
- also, who has access to sign the builds for distribution?
- 0.0.9.99-dev has been shared with the team for testing, report issues to: https://github.com/OmniLayer/omnicore/issues
- Adam
- Omniwallet
- Continuing to handling support / monitor updates from last week
- github
- private repos cleaned up
- plan downgraded to free
- Announcements mailing list
- announcement sent last week about omnicore 0.0.9.2
- Continuing cleanup of internal services
- Omniwallet
- Patrick
- Experimenting with instancing websocket servers to propagate trade data
- First round of bounty requirements
- Almost ready to integrate Omnicore
- Sean
- Focused on consulting projects last week
- Zathras
- Further work on feature activation by message for Omni Core
- OmniChest v6 development for MetaDEx and v0.0.10 features
- Minor bugfixes for Omni Core
Previous State of the Layer Post: