Search results

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)

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...

No way can we wait for them to become "open minded", the reason to implement IS should be economic. Or somehow technically force all their scripts to think 999999 confirmations has passed, just like Monero forces its privacy features. I hope DC team has some suggestions about the exchanges adoption

Now, the most important part of this update: get all the exchanges to respect ChanLocks and InstantSend :> I have sent requests to 7-10 exchanges in the past about adding InstantSend support, everyone of them returned the same response: "We will take this into consideration". And none of them...

Well, this does not clarify how the "enforced chainlocks" is different from "active chainlocks", but I get the point:D

Then why spork 19 (chainlocks) is not active? The upgrade scenario clearly states that chainlocks is enforced with dip8 activation

I believe, not "all" transactions are IS, but only those which were made with 4 or less inputs with 6+ blockchain confirmations each. So what is the ETA on full InstantSend implementation?

@akhavr is there any ETA on implementing InstantSend in Electrum?

This is regular DASH address, not a testnet

Special thanks for the interface changes (1 confirmation == fully confirmed) :) I also propose to remove the InstantSend checkbox, since it does nothing (doesn't it?) By the way, is it ok that some random transactions are still IS locked after 1600 confirmations, and others are not?

There are 3 unconfirming txs in my wallet, the first one is 2f82a026c08b8a1714e6db6f042e03aee00e254564d0d770b6059dfa465bf4e2 (raw attached below) UPD: It looks like I can't publish it, although the node is connected and fully synced. And the wallet reports that it is published UPD2: There is...

My payments are never confirming.. is this an issue on my side? I'm using rc3

Wow, thats cool So, are we going to have every dash transaction IS-locked after spork20 activation on mainnet? Without any exceptions, like number of inputs or anything else?

I have just made a transaction with 57 inputs. It should not be an autolock case, but it have been locked automatically. Do we have changes on that? UPD: The IS-lock is still active after 47 blockchain confirmations. And apparently not going to be removed anytime soon, hmmmmmmm.

done.

Yeah, I was just wondering what exactly is "a short period of time". An hour, day, or a week

When can we expect "SPORK_16_INSTANTSEND_AUTOLOCKS" activation?

Same behavior on 0.13.2. Sorry, I thought it was a bug

If I receive a transaction with wallet offline, and then start the Core, the wallet does not show the transaction in the list, unless it is confirmed in blockchain UPD: and there are problems with sending money during that time

This is good, should have been done a long time ago