-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Show NST/ERC1948 tokens on the Bridge UI #214
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 150.0 DAI (150.0 USD @ $1.0/DAI) attached to it as part of the LeapDAO fund.
|
Issue Status: 1. Open 2. Cancelled Workers have applied to start work. These users each claimed they can complete the work by 2 years, 8 months ago. 1) iamonuwa has applied to start work (Funders only: approve worker | reject worker). Spending my weekend on this task. ETA is before Sunday Learn more on the Gitcoin Issue Details page. |
@troggy is this issue still available? |
@pbteja1998 Gitcoin seemed to have some issues with this bounty — it appeared that I could only approve iamonuwa or travisdmathis, but not the other two people including you, unfortunately. I've posted at issue for Gitcoin here (gitcoinco/web#4486). I will post more bounties next week, you are very welcome to apply 🙏 |
@pbteja1998 if you are interested to get involved in LeapDAO community, please join our Slack: https://docs.google.com/forms/d/e/1FAIpQLSd8_wDGDAi__HvfYEWNK_bvJzIkxwHHRVL6AFEfJewBd2Vn9A/viewform We are interested in attracting long term contributors and have much more work to do, though we are posting only easier things to Gitcoin. |
@troggy I have joined the slack. Can you tell me which channels should I join specifically? |
Should I |
@troggy I am having problems with setting up the project. I am getting Is there something else that needs to be configured? |
@pbteja1998 yes, please. Unless @travisdmathis isn't changed his mind to work on this issue |
Ok, I have stopped work on gitcoin.
What about this? |
@pbteja1998 you can start with #new_contributors or jump in #20_d_for_development right away. Please reach out to |
@troggy i'm happy to take care of it for you, just approve it on gitcoin and i'll take it over. |
@travisdmathis should be already approved. Can you double check? |
@troggy ya, it looks like there's a gitcoin bug happening.. I never got a
notification that i was approved, it shows me as "work started" up top but it
doesn't show me as worker approved, still says I just submitted a request
for approval here.. It's actually showing Kevin as approved for work for me?
https://gitcoin.co/issue/leapdao/bridge-ui/214/3040
Not sure what's going on there, but i'll get to work on it this week 👍 and get it back to you.
…On Tue, May 28, 2019 at 12:15 AM Kosta Korenkov ***@***.***> wrote:
@travisdmathis <https://github.com/travisdmathis> should be already
approved. Can you double check?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#214?email_source=notifications&email_token=AAKF7HQZ4LD2MRZV34HTEP3PXSWUPA5CNFSM4HOUSYK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWK5LWQ#issuecomment-496358874>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKF7HWIESDYQSFOV4LABXTPXSWUPANCNFSM4HOUSYKQ>
.
--
Thank you,
Travis Mathis
|
@travisdmathis Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@travisdmathis UPD: well, hasn't been really registered. Investigating.. UPD2: it's in the bridge. Color 49153. So can be used for the purposes on this issue. Good luck |
@travisdmathis What's the status? Please submit WIP PR (at least) before Friday end of the day. Otherwise I will have to withdraw this one from you |
Hey @pbteja1998. Still interested in this bounty? It is available now — apply on Gitcoin |
@ericramos1980 👋Are you still interested? If so, please apply again (due to issue with Gitcoin your application is no active anymore) |
Issue Status: 1. Open 2. Cancelled The funding of 150.0 DAI (150.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter
|
1 similar comment
Issue Status: 1. Open 2. Cancelled The funding of 150.0 DAI (150.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter
|
Context:
All the tokens registered with the Leap Network receive a "color", a number from 0 — 655326 space. This color is being used in transactions to designate the token used by the transaction. The color space is split between tokens of different types like this:
Bridge UI shows the tokens registered on the network by reading them from contract. To get them, it checks if the color is taken by querying them one by one starting from the left boundary of the color space (e.g. 32769 for NFTs):
bridge-ui/src/stores/tokens.ts
Lines 123 to 133 in de34699
Problem:
Reading NST color space from the contract is not implemented. So even if you register an NST it won't be visible on bridge UI.
To do:
Optional (extra tips if any of these is complete as well):
Environment for test:
As of now, there is an NST token registered with a testnet, which is not visible on Bridge UI. To run the bridge UI with this network use
CONFIG=testnet yarn start
.The text was updated successfully, but these errors were encountered: