Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow an address to receive more than one DataCap assignment #5151

Closed
jnthnvctr opened this issue Dec 8, 2020 · 5 comments · Fixed by #6317
Closed

Allow an address to receive more than one DataCap assignment #5151

jnthnvctr opened this issue Dec 8, 2020 · 5 comments · Fixed by #6317
Assignees
Labels
P1 P1: Must be resolved status/blocked

Comments

@jnthnvctr
Copy link

jnthnvctr commented Dec 8, 2020

Client's can currently receive DataCap from a Notary at a given address. After spending that DataCap, if a Client wants more they have to provide the Notary with a new address in order to receive a new allocation of DataCap.

This introduces complexity for apps / users that require "top-ups" of DataCap. As an example - for an app like Slate they would need to behind the scenes monitor DataCap and usage for users (and swap out the addresses receiving and storing DataCap).

EDIT(@jennijuju)

Currently, datacap is assigned by notaries by using ./lotus-shed verifreg, which should be change to the ./lotus-shed notary terminalogy and also the cmd should be moving to a lotus cmd.

Instead of making a client verified client and then send a one-time upfront allocation, simply do a ./lotus notary send-datacap to allocate DataCap to a client account.

blocked by filecoin-project/specs-actors#1325

@jnthnvctr jnthnvctr changed the title Clients cannot receive DataCap from Notaries more than once. Clients cannot receive DataCap from Notaries more than once to the same address Dec 8, 2020
@jennijuju jennijuju changed the title Clients cannot receive DataCap from Notaries more than once to the same address Allow an address to receive more than one DataCap assignment Jan 19, 2021
@jennijuju jennijuju removed the product label Feb 15, 2021
@jennijuju
Copy link
Member

Reopen the ticket when FIP 0012 is accepted and implemented in spec actor

@jennijuju jennijuju reopened this Apr 2, 2021
@jennijuju
Copy link
Member

Reopening the issue as fip is now accepted and the actor implementation is ready filecoin-project/specs-actors#1390

@arajasek arajasek added this to the Network v12 Integrations milestone Apr 7, 2021
@jennijuju
Copy link
Member

Blocked by getting v4 actor dependency.

@jennijuju
Copy link
Member

blocked by #6022

@BigLep
Copy link
Member

BigLep commented May 14, 2021

Remaining work:

  1. Unit test in Lotus
  2. Get UX feedback from Product people and do anything requested (Refactor verifreg CMD #6194)

We can't close this until actors v5 is in master.

@jennijuju jennijuju added the P1 P1: Must be resolved label May 24, 2021
@BigLep BigLep linked a pull request May 26, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 P1: Must be resolved status/blocked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants