search

keyko-io / filecoin-verifier

Filecoin project issues
0 stars 0 forks source link

When choosing an address as a "Verifier", show the data cap associated with the address (if it exists) #3

Closed jnthnvctr closed 4 years ago

jnthnvctr commented 4 years ago

As a verifier, I will want to action the decisions I've negotiated off chain, by allocating data cap. In the current flow, I do this by choosing an address and allocating data cap to the client in question.

However, without knowing the data cap associated with an address I will have to cycle through many addresses in order to find one that still has cap remaining. Furthermore, as I spend data cap, I won't know how much I have available to me (in total) across all my addresses.

image

Proposal here would be to add a second column that: 1) Has a value, if a data cap is associated with the address 2) Has a NaN if no data cap associated with it

jernejpregelj commented 4 years ago

Screenshot 2020-09-21 at 12 42 06

aaitor commented 4 years ago

@josepablofm78 , can you test this one please?

jnthnvctr commented 4 years ago

tested and it works! one note - is it possible to get the same data cap rounding as we have in the other parts? mine says 100000000000000000 kib

On Tue, Sep 22, 2020 at 3:46 AM Aitor notifications@github.com wrote:

@josepablofm78 https://github.com/josepablofm78 , can you test this one please?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/keyko-io/filecoin-verifier/issues/3#issuecomment-696562805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFAHCS7BJALTVJVXMVFQ6DTSHBI4TANCNFSM4RAFWPGQ .

josepablofm78 commented 4 years ago

@jernejpregelj could you please take a look to this rounding issue?

jernejpregelj commented 4 years ago

Findings from looking into it: