Quick recap

The monthly Steering Committee meeting reviewed performance metrics and progress updates for various infrastructure proposals, with several partnerships and integrations in various stages of development. The team discussed potential payment arrangements and worker proposals, including bug fixes and contract enhancements, while exploring options for handling domain renewals and token codes. After careful consideration of costs and priorities, the committee ultimately approved only specific bug fixes while deferring other features for future consideration.

Summary

Core Infrastructure Performance Review

The monthly Steering Committee meeting reviewed September's performance for the Core Infrastructure Worker Proposal, which was under budget and saw increased domain registrations. Pawel reported progress on extending the existing Oracle to the Base platform for decentralized wrapping, aiming for a rollout this month. Wayne presented the Maintenance Worker Proposal's results, highlighting a revenue exceedance and successful partnerships, while Luke praised an innovative idea that significantly improved the foundation's financials.

Partnerships and Integrations Status Review

The team reviewed ongoing integrations and partnerships, with several partners including Urban, Quibbit, and Palma having signed MOUs for FIO integration. Wayne reported that multiple partners are actively working on integrations, with MetaMe and Let's Exchange expected to complete their integrations in Q1 2024, while Bitpanda Wallet is awaiting signature on their MOU. The team discussed a potential integration with CoinStore, where Wayne proposed a unique solution involving a $10,000 token loan to enable handle registration through the wallet, pending further discussion in tomorrow's meeting.

CoinStore Proposals and Strategy Review

The team discussed a potential payment arrangement where Wayne and Marie proposed a $10,000 token refund upon hitting registration benchmarks, though Pawel expressed concerns about the financial risk and emphasized the need to evaluate traffic and likelihood of success before approval. Luke reported that employee payments were proceeding smoothly, with funds being requested from market makers as needed while maintaining a market-neutral strategy. The conversation ended with Pawel preparing to review worker proposals, with Michael scheduled to present his proposal next.

Chain Development and Infrastructure Updates

The core infrastructure team no longer has any full-time chain developers, and Pawel discussed two potential releases: a contract release on the FIO chain and a FIP52 change requested by the Edge wallet to allow mapping contract addresses to field handles. Pawel explored options with a block producer who was unable to proceed, and now plans to pitch a new worker proposal to Ed and Michael for development. Additionally, a bug preventing domain renewals beyond a certain year was discovered, leading to a temporary cap on renewals to 50 years in the dashboard.

Worker Proposal Code Enhancement Discussion

Pawel and Michael discussed a worker proposal that addresses two issues: a code fix and a contract enhancement involving token codes. Michael submitted a FIP detailing these changes, noting that while the code fixes are straightforward, comprehensive testing is needed, especially for the contract address enhancement which affects multiple contracts. The proposal is still in draft, but Michael can set it to submitted if necessary.

Worker Proposal Development Timeline

Michael discussed a worker proposal with a 5-month timeframe, explaining that while the development work would likely be completed within 3 months, the overall process could be longer due to the MSIG process and potential issues with the Pheo chain. He outlined four main tasks: setting up the environment, addressing an overflow issue with domain expiration, developing token code enhancements, and preparing MSIGs for both testnet and mainnet. Michael noted that while the overflow issue only affects one contract, the token code enhancements would impact all contracts.

MSIG Deployment and Community Challenges

The meeting focused on discussing the deployment of MSIGs and community engagement challenges, with Michael, Pawel, and Ed using Telegram to request participation. Pawel pointed out a discrepancy in the worker proposal, which Michael confirmed could be reduced by $3,500 if the Steering Committee chooses not to proceed with Task 3. Wayne inquired about the technical aspects of mapping contract addresses, and Pawel explained the differences between current token codes and the proposed changes, emphasizing the need for a standard to support contract address mappings without on-chain development.

Worker Proposal Budget Decision

The Steering Committee discussed a worker proposal submitted by Michael for bug fixes and potential FIP implementation. Pawel suggested focusing only on the bug fix due to current financial constraints, while Emily proposed splitting the proposal into two separate efforts. The group debated the merits of combining or splitting the proposals, with Wayne and Pawel agreeing that splitting could be more expensive due to overlapping tasks. Michael offered the possibility of a phased approach, allowing for the second effort to be added later if budget allows. The committee decided to seek consensus on whether to approve the full proposal, split it, or focus only on the bug fix, with Pawel emphasizing the importance of fixing the domain renewal bug.Bug Fix Approval and Future Review

The steering committee discussed a proposal involving bug fixes and contract-based token requests. After considering the costs, potential usage, and importance of the 100-year renewal feature, they decided to approve only the bug fix, with Pawel and Wayne as the main supporters of this decision. The committee agreed to revisit the 100-year renewal feature at a later time, especially if there is increased demand from partners like Edge.

Next Steps

• Pawel to inform Michael that the Steering Committee decided not to proceed with the worker proposal for the bug fix and FIP52 at this time.

• Pawel to publish a specification for contract address support in FIO requests without on-chain development to accommodate Edge's request.

• Wayne to follow up with CoinStore regarding potential integration terms after their call tomorrow morning.

• Wayne to travel to Guyana next week to meet with their government about potential FIO integration.

• Core team to continue working on base wrapping for FIO tokens.

Video