-
Notifications
You must be signed in to change notification settings - Fork 18
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
Bayou: Bulk transfer tool for both FT and NFT #onFlow #79
Comments
great, thank you @LanfordCai |
Hi @LanfordCai! On this proposal, could you please include an adoption milestone (similar to your other proposal) and also propose a specific timeframe for how long you intend to support against the Maintenance milestone? Thanks! |
Hi, @chrisackermann ! Thank you for your feedback! I have added the adoption milestone and the timeframe. For the adoption, Bayou send the fund/NFTs directly by using a single For the timeframe, in fact, I'll maintain it as long as I can. |
Hi @LanfordCai - we've reviewed and just had a few small follow-up questions for you:
|
Hi Chris!
|
Hi @LanfordCai, thanks for your patience! I just wanted to let you know that we've accepted your proposal and will be following up directly via email with next steps. Thanks! |
Grant category
Please select one:
Description
Problem statement
With the blooming of DAOs, bulk transfer is an increasingly important feature for community operation in Web3. It would be annoying and inefficient for an operator to send tokens to the recipients one by one.
Currently, we have built a tool named bayou for the bulk transfer of Fungible tokens, and it works well so far:
but there is still no universal NFT bulk transfer tool now, and we want to add this to bayou!
Proposed solution
We are going to add some features to bayou to support the NFT bulk transfer and improve user experience:
The NFT bulk transfer feature is not only an input field for users to input tokenIDs, but comes with a much more user friendly click-to-choose UI, like what's on drizzle:
Impact
Milestones and funding
Team
discord: lanford33#2178
The text was updated successfully, but these errors were encountered: