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

R4R: BEP84 mirror and sync #84

Merged
merged 3 commits into from
Jan 19, 2021
Merged

R4R: BEP84 mirror and sync #84

merged 3 commits into from
Jan 19, 2021

Conversation

abelliumnt
Copy link
Contributor

Currently, if a user wants to issue and bind a BEP2 token with an existing BEP20 token, it has to do a set of complex operations, including issue BEP2 tokens, sending a bind transaction and approving the binding request. The BEP will bring a mechanism to simplify the above process. In the new mechanism, what anyone can do this is just sending a transaction to Binance Smart Chain.

@abelliumnt abelliumnt force-pushed the mirror-sync branch 4 times, most recently from 613149a to e7dff46 Compare December 14, 2020 08:27
@48ClubIan
Copy link
Contributor

This can be excellent!
Actually, we are currently considering issuing the BEP2 version of our token and bind them, but the protocol is too tricky for us even on test net.

Looking forward to this BEP

BEP84.md Outdated Show resolved Hide resolved
BEP84.md Show resolved Hide resolved
BEP84.md Outdated Show resolved Hide resolved
BEP84.md Outdated Show resolved Hide resolved
BEP84.md Outdated Show resolved Hide resolved
BEP84.md Outdated Show resolved Hide resolved
BEP84.md Outdated Show resolved Hide resolved
@abelliumnt abelliumnt dismissed a stale review via de55d23 January 11, 2021 01:45
unclezoro
unclezoro previously approved these changes Jan 19, 2021
HaoyangLiu added 2 commits January 19, 2021 11:25
update error code

update channel id

remove refundAmount

trace if a bep20 is bound by mirror
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants