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

Integrate ShapeShift #1

Open
ethernomad opened this issue Feb 16, 2017 · 3 comments
Open

Integrate ShapeShift #1

ethernomad opened this issue Feb 16, 2017 · 3 comments

Comments

@ethernomad
Copy link
Contributor

No description provided.

@ethernomad
Copy link
Contributor Author

ShapeShift said the following:

so the basics of it are that you would do an integration either with our api or our shifty button. and it would include some key pieces of data that would allow us to route your transactions a bit differently from normal trades in our system.

[1:31]
What we've found to be easiest is you would create an integration with ShapeShift that does a normal BTC -> ETH transaction. However, in your transaction you would include your affiliate key and for the 'withdrawal address' you would use the address given by your users (ie where they want the token sent).

[1:32]
For the user perspective they just used your site and sent BTC and will (eventually) receive your token.

[1:32] the 'eventually' statement is assuming you are collecting funds and then giving them out at a later date after teh sale ends. otherwise you could just send your token to the users address immediately but thats up to you. (edited)

[1:32] On our side - we will add a bit of code to our order processing that any time we see a transaction with your affiliate key we will swap the users withdrawal address out and use the address of the TOKEN contract. And we will send the users address to a particular function on the contract.

[1:33] What i would need from you to get this coded on our side is:

  1. Once you've talked with Emily and gotten an affiliate key setup for vanbex I'll need to know what the key is.
  2. I'll need to know the address of the TOKEN contract.
  3. I'll need the hash prefix for the function call to use. Generally in the past its looked roughly like: 0xaaaaaaaaabbbbbbbbbbbbbbbbbbbbbbbbbb where the a's are the function hash prefix and the b's are the users address that i concatenate on and that gets sent as 'data' in the ethereum transaction.

Let me know if this will work for you all. And feel free to ask me any other questions you have.

@ethernomad
Copy link
Contributor Author

This is exactly what we need, even for purchasing VIP with Ether. It gets around the problem of regular payment transactions not supplying enough gas.

@ethernomad ethernomad modified the milestone: VIP MTO starts Feb 16, 2017
@Mogul007
Copy link

Ok so what do you suggest we do then?

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

2 participants