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

Add a client demo that requests airdrops from solana-drone #343

Closed
5 tasks done
garious opened this issue Jun 12, 2018 · 5 comments
Closed
5 tasks done

Add a client demo that requests airdrops from solana-drone #343

garious opened this issue Jun 12, 2018 · 5 comments
Assignees
Milestone

Comments

@garious
Copy link
Contributor

garious commented Jun 12, 2018

solana-client-demo is configured with mint-demo.json, which includes mint's keypair. That gives the demo access to all unallocated tokens. We need a new client demo that doesn't have access to that keypair and instead requests tokens from solana-drone (#342). Using the drone to request an airdrop will allow many different users should be able to run this demo without concern that tokens will all be used up by another user.

  • client creates or loads a keypair
  • We run solana-drone as a daemon on a machine that has a public ip, preferably testnet.solana.com (see Set up leader on cloud service #307)
  • client make TCP request to testnet.solana.com:DRONE_PORT
  • client request should include the public key of the client
  • drone should make a transaction from the mint to the client public key
@garious garious changed the title Add a new client-demo to optionally request tokens from solana-drone Add a client demo that requests airdrops from solana-drone Jun 12, 2018
@garious garious added this to the v0.7.0 milestone Jun 12, 2018
@garious
Copy link
Contributor Author

garious commented Jun 13, 2018

@aeyakovenko, can you help us scope this ticket? After this client demo gets some tokens, what should it do? We already have a TPS-focused demo. Should this one do something much simpler like send a handful of transactions and check up on them?

@aeyakovenko
Copy link
Member

aeyakovenko commented Jun 13, 2018

@garious edited

@mvines mvines self-assigned this Jun 15, 2018
@mvines
Copy link
Member

mvines commented Jun 16, 2018

My current plan is to fix #307 first then use the cloud infra developed there to run the drone as well. @CriesofCarrots, I'm guessing you're working on #342 first as well?
Seems like once either of us has finished our respective dependent issue we can rendezvous back here and figure out who does what next.

@CriesofCarrots
Copy link
Contributor

Yes, exactly, sounds great.
Right now, the drone's sole function will be to make an airdrop of sols to the public key of a requesting client. That should enable the client demo to perform basic user functions, like send transactions, check transaction status, and check balance. But if you can foresee anything else we might need from the drone for this ticket, do let me know.

@mvines mvines removed their assignment Jun 26, 2018
@mvines
Copy link
Member

mvines commented Jun 26, 2018

De-assigning myself, as the infra part of this is all done. If I can help with something else here please LMK

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

No branches or pull requests

4 participants