Timeline for Wallet, deposit and withdrawal management system or APIs
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 26, 2020 at 9:33 | comment | added | firepol | @Murch I edited the question, so now it's more generic and not anymore hyp oriented. I realize that if I want to code my own crypto exchange, the requirements would be very similar... | |
Feb 26, 2020 at 9:31 | history | edited | firepol | CC BY-SA 4.0 |
Removes HYP use case and made question more generic and more interesting
|
Feb 26, 2020 at 9:23 | answer | added | firepol | timeline score: 0 | |
Oct 17, 2019 at 11:54 | comment | added | firepol | @chytrik the actually pay... for a while. I was fascinated on how their infrastructure works so well and wondering if they probably implemented their own solution/wrapper or if they use something existing like the answer below suggest: bitgo or another famous service. | |
Oct 16, 2019 at 23:30 | comment | added | Murch♦ | This is a bit of an "XY-Question". Your main question seems to be about best practices for integrating cryptocurrency payments with a website. The HYIP context appears to be just an example in which you've seen a similar solution than what you're looking for. This question could therefore be improved by editing topic and body to focus on the main inquiry instead of the HYIP use-case. | |
Oct 16, 2019 at 23:24 | history | edited | Murch♦ |
edited tags; edited tags
|
|
Oct 16, 2019 at 23:12 | comment | added | chytrik | I'd imagine that an HYIP scam site doesn't really need any customer-specific infrastructure, since they are scams that won't pay out anyways. | |
Oct 16, 2019 at 22:16 | answer | added | Raghav Sood | timeline score: 2 | |
Oct 16, 2019 at 22:15 | review | First posts | |||
Oct 17, 2019 at 9:12 | |||||
Oct 16, 2019 at 22:11 | history | asked | firepol | CC BY-SA 4.0 |