|
| 1 | ++++ |
| 2 | +tags = ["dev-meeting", "front-page"] |
| 3 | +title = "Weekly Developer Meeting" |
| 4 | +date = 2025-02-07 |
| 5 | ++++ |
| 6 | + |
| 7 | +### **Freenet Sync Meeting Summary – Ian Clarke & Ignacio Duart (2025/02/07 08:45 CST)** |
| 8 | + |
| 9 | +#### **Attendees** |
| 10 | +- Ian Clarke |
| 11 | +- Ignacio Duart |
| 12 | + |
| 13 | +#### **Key Updates & Discussion Points** |
| 14 | + |
| 15 | +1. **Network Connection Fixes** |
| 16 | + - Most issues preventing stable peer connections have been fixed. |
| 17 | + - The network can now maintain multiple connections, resolving a previous issue where only two peers could connect at a time. |
| 18 | + - The root cause was a combination of: |
| 19 | + - The gateway not waiting long enough before cleaning transient connections. |
| 20 | + - A logic bug in packet receipt handling that caused repeated transmission loops. |
| 21 | + - A fix was implemented to send receipts after a time threshold, even if the packet count limit wasn't met. |
| 22 | + |
| 23 | +2. **Remaining Network Issue** |
| 24 | + - There is still a logical issue in peer filtering when forwarding new connection requests. |
| 25 | + - Some peers are mistakenly being filtered out, preventing them from establishing connections. |
| 26 | + - Ignacio believes the issue stems from unintended state mutations in transaction forwarding logic. |
| 27 | + |
| 28 | +3. **Ping Contract Debugging** |
| 29 | + - The team was testing the ping contract using a single peer for writes and others for reads. |
| 30 | + - An issue was discovered where state updates are not propagating, likely caused by a previous efficiency optimization that prevented redundant updates. |
| 31 | + - The get function may also not be retrieving the contract correctly. |
| 32 | + |
| 33 | +4. **Demo & Deliverable Strategy for Filecoin** |
| 34 | + - Filecoin's representative likely just needs documentation proving progress rather than a live demo. |
| 35 | + - The plan is to: |
| 36 | + - Ensure a version is published that users can install. |
| 37 | + - Demonstrate the ping contract working via a recorded video rather than a live presentation. |
| 38 | + - Aiming to send materials by **Friday, February 14**, avoiding a last-minute submission. |
| 39 | + |
| 40 | +5. **Persistent Contract Updates for Demo** |
| 41 | + - To ensure the contract is continuously updated, the team will run the ping contract on a gateway to keep activity visible. |
| 42 | + |
| 43 | +6. **Code & Technical Adjustments** |
| 44 | + - Discussed removing an outdated connection filtering rule preventing multiple nodes on the same local network from connecting. |
| 45 | + - Ensured that the network can support multiple peers with the same location, using historical response times for routing decisions. |
| 46 | + |
| 47 | +7. **River Chat Integration & Serialization Issue** |
| 48 | + - Ian is working on integrating River with Freenet. |
| 49 | + - Encountering a serialization error when sending messages via WebSockets. |
| 50 | + - Ignacio suggested debugging the contract execution process by adding logging inside the contract functions. |
| 51 | + - Suspected issue: The contract is failing to deserialize state data inside the WASM execution layer. |
| 52 | + |
| 53 | +#### **Next Steps** |
| 54 | +- **Ignacio** will continue debugging the contract issue and monitor network stability over the weekend. |
| 55 | +- **Ian** will investigate the serialization error in River and implement contract logging to pinpoint the deserialization issue. |
| 56 | +- **Both** will work toward a stable release early next week, with a recorded demo prepared by midweek. |
| 57 | + |
| 58 | +#### **Closing Notes** |
| 59 | +- Ignacio mentioned a tool for creating realistic AI-generated demo videos with avatars; he will follow up with Ian on its name. |
| 60 | +- Ignacio had to leave for family obligations, and the meeting concluded at **00:56:00**. |
0 commit comments