4 ms·
The roadmap is misleading - sorry, that feature is code complete and awaiting integration. Our approach to resource usage is that peers keep track of the resou
by sanity31415 3y ago
The roadmap is misleading - sorry, that feature is code complete and awaiting integration.
Our approach to resource usage is that peers keep track of the resources used by each contract or on behalf of each neighboring peer, and compares it to the value provided by the contract or neighboring peer to our peer or the network. Peers or contracts with the least bang for the buck will get dropped by the peer when it is resource constrained. See [1] for how this works with contracts, and [2] for implementation.
[1] https://github.com/freenet/locutus/issues/244 https://github.com/freenet/locutus/issues/244
[2] https://github.com/freenet/locutus/blob/3e5a31780f235e04f7b22d8face93a05141568f5/crates/locutus-core/src/resource_manager/mod.rs#L42 https://github.com/freenet/locutus/blob/3e5a31780f235e04f7b2...
- projektfu 3y agoCool thanks
- creamyhorror 3y agoWhile your concept and cost/decision function covers more than just storage, the topic of resource allocation brought to mind the old Japanese P2P software called Perfect Dark (https://en.wikipedia.org/wiki/Perfect_Dark_(P2P) https://en.wikipedia.org/wiki/Perfect_Dark_(P2P)), which used an unrevealed algorithm to distribute files across participants' volunteered disk storage. Its architecture was similar to Freenet's, "only with a heavier use of distributed hash tables."