InstantSend exchanges and wallets adoption

f8192

New Member
Dec 17, 2017
27
4
3
31
InstantSend exists since 2015, but almost all major exchanges failed to implement InstantSend so far. This article on DashNews states a very reasonable message: users and merchants having to take additional action was a huge no-go. There is absolutely no reason for the exchanges to move a finger to adopt DASH cool features. And while checking confirmations was more secure in some cases than relying on InstantSend lock during pre-ChainLocks era, nowadays it is totally redundant.
I propose to DASH Core team an idea of forcing everyone to update their scripts, by rewriting DASH-daemon RPC calls, without legacy code support. There should be no easy access to confirmations count, only to the fact of IS or CL lock.
I don't think DASH will be removed from a single exchange because of that, so in worst case scenario the situation remains, but in best.. uh.. we will have fast and usable DASH everywhere, and growing users count.
To be discussed...
 
Last edited:
  • Like
Reactions: GrandMasterDash

f8192

New Member
Dec 17, 2017
27
4
3
31
Or even better: in case of requesting a confirmations number of a transaction with old-style scripts, and if transaction was IS or CL locked, return 999999999, or 0 otherwise.
(and of course mark this call as deprecated)