Skip to content
Home » Meeting Summaries – Cuprate

Meeting Summaries – Cuprate

Below are the latest meeting summaries. Expand the table of contents below to jump to a particular date.

Cuprate Meeting Summaries

Jan 7, 2025

Source: Github Logs
AI Summary:

  • Attendance and Updates:
  • Present: boog900, syntheticbird, hinto, kayabanerve, malori
  • boog900: Finished ‘init’ PR and 32-bit support PR, started reviewing RPC handlers PR
  • hinto: Posted CCS update, working on roadmap writeup for 2025
  • syntheticbird: Provided comments on ‘init’ PR
  • Cuprate Development Discussion:
  1. Database:
  • Consideration of using LMDB bindings directly instead of ‘heed’
  • Discussion on multimap table support for FCMP++
  • Debate on storage efficiency and performance
  1. RPC Integration Plan:
  • Create generic ‘monerod’ <-> ‘cuprated’ RPC testing harness
  • Focus on wallet2 required calls, then frequently used calls
  1. FCMP++ Compatibility:
  • Discussion on timeline for FCMP++ integration
  • Assumption of sufficient window before FCMP++ goes live on monerod
  • Cuprate Branding Discussion:
  • Debate on changing Cuprate’s motto
  • Suggestions included emphasizing performance, independence, and Rust implementation
  • Concerns raised about claiming security without proper audits
  • No final decision made on new motto
  • Miscellaneous:
  • Brief discussion on Nim programming language
  • Joke about implementing FCMP++ in Zig

Closing summary:
The meeting covered various aspects of Cuprate development, from technical discussions on database implementation to branding considerations. Key points included the potential shift to direct LMDB bindings, plans for RPC integration, and the timeline for FCMP++ compatibility. The team also engaged in a lengthy discussion about Cuprate’s motto, highlighting the challenges of accurately representing the project’s attributes. While no final decisions were made on the motto, the discussion emphasized the importance of careful wording in project descriptions. The meeting concluded with agreement on the importance of Cuprate being ready for FCMP++ implementation alongside monerod.

Dec 17, 2024

Source: Github Logs
AI Summary:

  • Greetings and updates:
  • boog900 is back to work on Cuprate after a brief hiatus
  • hinto implemented an ‘Entry’ API for cuprate_database, finished draft RPC handler functions, and created a testing harness for monerod <-> cuprated compatibility
  • syntheticbird plans to update the website and link docs
  • Project discussion:
  • Plans for RPC input/output compatibility testing were discussed
  • A code snippet for potential implementation was shared and discussed
  • Concerns about monerod’s RPC throughput were raised
  • RandomX full memory mode integration:
  • Discussed how to implement it in cuprated’s config
  • Explored the current implementation and potential improvements
  • Discussed pipelining for dataset creation
  • GPU usage for Bulletproof(+):
  • syntheticbird inquired about the possibility of optional GPU acceleration support
  • boog900 expressed openness to the idea if it provides significant performance boost and is audited

The meeting covered recent updates, future plans, and technical discussions for Cuprate. Key topics included RPC compatibility testing, RandomX integration, and potential GPU acceleration. The team’s focus on compatibility, performance, and thorough testing highlights their commitment to developing a robust and efficient product. These discussions will guide Cuprate’s ongoing development and feature implementation.

Dec 10, 2024

Source: Github logs
AI summary:

• boog900 reported being ill for the past week
• hinto combined RPC handlers into a single PR and started a skeleton for the User Book
• Discussion about boog900 taking a break after PR #344 is merged
• Identified remaining tasks for initialization: implementing heed get_range and cleaning up the PR

Overall the Cuprate meeting was brief, with boog900 reporting illness and hinto sharing progress on RPC handlers and the User Book. They discussed the possibility of boog900 taking a break after merging PR #344. The main tasks remaining for initialization were identified as implementing heed get_range and cleaning up the related PR. The meeting concluded with thanks from participants.