Skip to content
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.

Releases: myelnet/pop

v0.1.1

11 Jan 23:18
9838282
Compare
Choose a tag to compare
refactor: ppb for content delivery as a flag (#246)

* refactor: remove region based pricing

* feat: ppb flag for setting serving price data

* fix: ppb types

* fix: clearer prints

Co-authored-by: tchardin <[email protected]>

* fix: clearer provider-client differentiation in prints

Co-authored-by: tchardin <[email protected]>

v0.1

28 Oct 11:10
9b114b0
Compare
Choose a tag to compare

This is an alpha release featuring end to end retrieval market capabilities including content routing, replication and transfer.

Base features:

  • Free and paid data transfers.
  • Gossipsub based content routing using recursive message forwarding to send responses.
  • Publish records to a remote index if an optional url is provided.
  • Light wallet interface to interact with the local keystore and send messages to a remote lotus node RPC in order to transfer funds in and out of the node's wallet.
  • Access a key in the local keystore to sign a new payment channel message.
  • Send chain messages to a remote lotus node RPC.
  • Manage the lifecycle of payment channels, store vouchers locally.
  • Retrieve content from a Filecoin storage provider.
  • Maintain a log of all request to rank content by usage frequency
  • Ability to sync provided blocks from a nearby peer when joining the network for the first time.
  • Dispatch new content to cache providers given a replication factor.
  • Decision mechanism for deciding whether to store an incoming block or not. (accept all by default)
  • Priority cue to garbage collect least frequently used content.
  • Set different strategy levels for selecting providers including:
    • First response with given price ceiling.
    • Cheapest price in given time period.
  • Import content from CAR file.
  • HTTP gateway for posting and getting content.
  • TLS certificate generation via Certmagic to enable secure websocket transport with browser clients.
  • Observability and benchmarks for retrieval operations.
  • Testground plans to test the network at different scales.

v0.1-rc2

22 Jun 13:14
580a109
Compare
Choose a tag to compare
v0.1-rc2 Pre-release
Pre-release
feat: fetch and list transaction entries without retrieving linked da…

v0.1-rc1

03 May 10:11
Compare
Choose a tag to compare
v0.1-rc1 Pre-release
Pre-release

This is a first release candidate which provide end to end retrieval market features including content routing, replication and transfer.

Base features:

  • Free and paid data transfers.
  • Gossipsub based content routing using recursive message forwarding to send responses.
  • Light wallet interface to interact with the local keystore and send messages to a remote lotus node RPC in order to transfer funds in and out of the node's wallet.
  • Access a key in the local keystore to sign a new payment channel message.
  • Send chain messages to a remote lotus node RPC.
  • Manage the lifecycle of payment channels, store vouchers locally.
  • Create a storage deal with a Filecoin storage provider.
  • Retrieve content from a Filecoin storage provider.
  • Settle payment channel automatically.
  • Automatically collect payment channel after the wait period.
  • Maintain a log of all request to rank content by usage frequency
  • Ability to sync provided blocks with a neary peer when joining the network for the first time.
  • Dispatch new content to cache providers given a replication factor.
  • Decision mechanism for deciding whether to store an incoming block or not. (accept all by default)
  • Priority cue to garbage collect least frequently used content.
  • Set different strategy levels for selecting providers including:
    • First response with given price ceiling.
    • Cheapest price in given time period.
  • Keep track of previous successful providers to increase speed of provider selection.
  • Observability and benchmarks for retrieval operations.
  • Testground plans to test the network at different scales. (Due to some Testground issues it is not possible to run beyond 47 instances currently and requires debugging from the maintenance team)