Skip to content

Milestones

List view

  • IPFS Pinner Service

    Monitor log events for on-chain registry // Attempt to pin manifests from log events // Maybe do some simple verification of manifests? Ensure they’re not garbage. // Maybe backup assets somewhere? - Is this a Trinity plugin?

    No due date
    0% complete0 open0 closed

  • Publish a Package on my Registry

    Retrieve the standard registry package // Instantiate an instance pointed at the user’s registry // Push package assets to IPFS (infura) // Use the registry contract to publish the package. [py-ethpm wrapper around web3?][web3 check that it's connected to main chain - (if not error?)]

    No due date
    0% complete0 open0 closed

  • Package Up My Contracts

    Construct a Package instance with the appropriate contract assets. // Generate JSON-Document from the Package Instance

    No due date
    0% complete0 open0 closed

  • Create a Package Registry

    Retrieve the standard registry contract package using web3.pm API // Pull the ContractFactory for the standard registry // Create registry package // Deploy a standard registry contract // (optionally) tie it to an ENS name or subdomain.

    No due date
    0% complete0 open0 closed

  • Access a Deployed Contract

    Load the package from a URI // Use Web3.py to load the package and retrieve the contract instance // Interact with the contract.

    No due date
    0% complete0 open0 closed

  • `py-ethpm` without compilation

    Deploy an ERC20 token using the erc20 package :: ( Load the package from a URI // Use Web3.py to load the package and retrieve the ContractFactory for the ERC20 token // Use standard Web3.py APIs to deploy)

    No due date
    0% complete0 open0 closed