Are we expecting any news/updates soon on anything in the pipeline  I made a pull request for a few changes. If you want to be an early bird, check this https://github.com/Nite69/sync- version number update to 1.0.4 - protocol version to 60019 - don't download blocks from older versions - checkpoints at ( 86401, uint256("0x07b09d7985b5c0f68d3e5608d49361397e767ac8101433b00ad3bd73bc91dfd1")) ( 87840, uint256("0xb8ebf4e9c2ba68e0804f55ceb44cd678349333e14507f3ff3ca263fdb2bd88e9")) ( 88825, uint256("0x4a1495914f815f9923ab84ff20b627200acb6be563b025ee3f6e41a6750ca550")) This is not mandatory update, but will anyway help stabilizing the blockchain after stake change. |
|
|
|
|
Yes, it is working now. Ty all, have to go to sleep. GN!
|
|
|
|
I really should set up this windows box of mine so i can compile windows wallets. I hate waiting for someone to compile it
I guess there is no need to compile a windows version for this. Current version will work fine after next block is found. |
|
|
|
There is a bug which prevents block number 86400 being found.. but after it is found, also current wallet works fine. There is a fix on the github, however this update is not necessary to all, we only need some wallets to update to find the first block and get the chain moving. So all volunteers, please update. https://github.com/MsCollec/sync if that was up five minutes ago, I'm compiling it now. Sorry, I was one of the stragglers. Thought I had updated, but I hadn't. Dumb oversight. Do I need to delete the blockchain and resync? No need to delete & resync. just compile and run. |
|
|
|
There is a bug which prevents block number 86400 being found.. but after it is found, also current wallet works fine. There is a fix on the github, however this update is not necessary to all, we only need some wallets to update to find the first block and get the chain moving. So all volunteers, please update. https://github.com/MsCollec/sync |
|
|
|
I'm worried about this; 18 minutes and only old version gets blocks. That means majority of the coins are on old wallets. We might be forced to downgrade and postpone the interest halving.
Anyone seen Mscollec?
No, this is bad idea. We need simply wait till block find and diff down nite NO rollback please at this time - just wait - if the fork appears with the new block the others HAVE to update or get orphans Yes, I don't like it either, but we might be forced to do that. The height of the old chain is already 86441 blocks. |
|
|
|
|
I'm worried about this; 18 minutes and only old version gets blocks. That means majority of the coins are on old wallets. We might be forced to downgrade and postpone the interest halving.
Anyone seen Mscollec?
|
|
|
|
just download the latest Version - and Forget about this discussion
is there a new wallet version now? im still in v1.0.3.0 1.0.3 is correct version. So is 1.1.0, which has nitesend BETA *and* interest halving. But there seems to be a lot of old versions still running. That is the problem. Postponing 9 reconnects
REORGANIZE
REORGANIZE: Disconnect 0 blocks; 8d5cb9d824806864d9d0..8d5cb9d824806864d9d0
REORGANIZE: Connect 1 blocks; 8d5cb9d824806864d9d0..c6eea8784932e513d750
ERROR: ConnectBlock() : coinstake pays too much(actual=95281 vs calculated=47640)
ERROR: Reorganize() : ConnectBlock c6eea8784932e513d750 failed
InvalidChainFound: invalid block=0acd10398ecc6a2855f0 height=86409 trust=28213769055520333 blocktrust=965175 date=27.07.2014 20:59:42
InvalidChainFound: current best=8d5cb9d824806864d9d0 height=86399 trust=28213769040964854 blocktrust=4061659 date=27.07.2014 20:48:12
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
|
|
|
|
I'm still wondering these problems that are related to coinjoin in general. There are 2 main problems: If there is not any other transaction to join, there won't be any nitesend/coinjoin transaction. The other problem is that when generating the joined transaction, someone who peeks and logs *all* transaction offers 24/8 would find out some information about coin owners.
But there are solutions to fix these. One idea to fix the first would be 'spontaneous nitesend mixer'. The basic idea is to allow wallets to collectively mix their coins to a brand new, first time used coins. This mixing transaction could happen either on predefined time or after wallets collectively find enought participants. In practise that would mean: you check the 'mix my wallet' checkbox. Wallet broadcasts a mixing request and counts all received requests. When a treshold has been reached, all wallets send one transaction with random sized newly generated output coins. This could be repeated just as often as wanted.
What about block chain bloat? Implementing this solution in a way that isn't easy to trace will require a lot of "mixing" transactions. It will take time for those transactions to confirm, slowing the overall nitesend transaction time and adding extra "bloat" to the block chain. Of course, it will fill the blockchain with some extra transactions, but I would not be worried about it's effect on the size. If we look at the transaction amount on bitcoin, there will be no problem. One would not need to do it very often. If you mix your complete wallet and distribute it to 20 different coins, and 10 other ppl are doing the same, it mixes the taint analysis quite well. But I originally noted they should be random sized; actually defined size is better. Otherwise peeker would be able to count which input group sums upp to what output group. But if there is 200 coins of size 0.01, it is impossible to tell which output was coming from what input.
Another idea to prevent peeking the nitesend transactions would be using crypted communication. In this case, we could use for example hyperboria (cjdns) technology; combined with sync, that would mean all sync coins would have an own ipv6 address and an encrypted communication link! Nitesend transaction could be collected by sending the offers throught these kind of links, securing them from all peekers. Actually, the whole comunication between peers could be done throught private hyperboria network. I guess it would be better than TOR and vpn together.
What do you think? The problem is that these (specially nr 2) need some work to do and I really am not sure if they are worth implementing. Would they add enought anonymity to be worth implementing?
This to me seems ambitious. Not going to say impossible because I don't know much about cjdns, just what it does. I think this could work but it would not be simple. The first question to ask, does this mean each of the smallest fractions of sync (i.e. 1 satoshi) will have an ipv6? Who initially determines the table and how is it verified? In order for it to work if I understand, there is a distributed hash table with all of the stored network addresses, so how do you drop that on the network? No, not every satoshi has an ipv6 address, but every sync address has also an ipv6 address. In cjdns the address is practically a public key of a secret key. And the secret key of an sync address implicitely already have a cjdns ipv6 address. You are right, it would not be simple. But if done, it would bring the benefits of TOR and vpn, and also UDP communication instead of TCP. |
|
|
|
In the current version, the transaction that does not get finished, are just cancelled. This will change in the final verison.
My questions about transactions still have not been answered. Nitesend in its current form is NOT anonymous. Its more of a muddling service than an anon service. It just groups transactions together but the inputs and outputs remain the same. Smaller transaction groups (2,3,etc) could easily be traced with reasonable certainty. How does Nitesend address this? I'm still wondering these problems that are related to coinjoin in general. There are 2 main problems: If there is not any other transaction to join, there won't be any nitesend/coinjoin transaction. The other problem is that when generating the joined transaction, someone who peeks and logs *all* transaction offers 24/8 would find out some information about coin owners. But there are solutions to fix these. One idea to fix the first would be 'spontaneous nitesend mixer'. The basic idea is to allow wallets to collectively mix their coins to a brand new, first time used coins. This mixing transaction could happen either on predefined time or after wallets collectively find enought participants. In practise that would mean: you check the 'mix my wallet' checkbox. Wallet broadcasts a mixing request and counts all received requests. When a treshold has been reached, all wallets send one transaction with random sized newly generated output coins. This could be repeated just as often as wanted. Another idea to prevent peeking the nitesend transactions would be using crypted communication. In this case, we could use for example hyperboria (cjdns) technology; combined with sync, that would mean all sync coins would have an own ipv6 address and an encrypted communication link! Nitesend transaction could be collected by sending the offers throught these kind of links, securing them from all peekers. Actually, the whole comunication between peers could be done throught private hyperboria network. I guess it would be better than TOR and vpn together. What do you think? The problem is that these (specially nr 2) need some work to do and I really am not sure if they are worth implementing. Would they add enought anonymity to be worth implementing? |
|
|
|
In the current version, the transaction that does not get finished, are just cancelled. This will change in the final verison.
My questions about transactions still have not been answered. Nitesend in its current form is NOT anonymous. Its more of a muddling service than an anon service. It just groups transactions together but the inputs and outputs remain the same. Smaller transaction groups (2,3,etc) could easily be traced with reasonable certainty. How does Nitesend address this? Nitesend is quite much an implementation of this https://bitcointalk.org/index.php?topic=279249.0The coinjoin idea itself is not a complete answer to the anonymity of cryptocurrency transactions. However, AFAIK, there is currently no any better anonymous implementation on any coin. There is also some ideas which might be implemented using nitesend to increase anonymity; an extra fee, which could be used to get more wallets to mix the transaction even more; automatic wallet mixing feature, ie all (of those who want) wallets collectively change their coins to newly generated random-sized coins, using nitesend. Actually, this implementation could also used as a centralized system; an organization could put up a wallet running this, all wallets inside the organization could mix the transactions behind open internet. Just a few ideas. But you are right, nitesend (or any coinjoin) is not a complete solution. However, it does add anonymity. |
|
|
|
Hi!
Source for the beta version of the nitesend wallet is ready, I'm just building a compiler environment for the windows environment. I'm not sure if I can finish it today (it's 3 am here, 'yesterday'), but you will get it tomorrow (eh, today).
It won't be the final version yet, but the essential parts are working, so all who want to test it, can do that.
Biggest missing parts are correct handling of the situations when something can go wrong, ie, if the transaction cannot be completed. However, on these cases, the transaction just won't go throught. On the final version it will roll back and make another try until success.
Also, there is already a server running the nitesend wallet. You can add it to your .conf, ip is 95.85.31.58
EXCELLENT WORK NITE! Do we use real sync to test or test coins I have been using real coins from the beginning :-) Have not lost any. At the beginning, I needed --salvagewallet a few times, but not any more. Of course, this is still quite early version, so I would not recommend to use big money for tests. Anyway, if you are careful with the addresses you send coins and keep a backup of your wallet.dat, you should be safe. |
|
|
|
|
Hi!
Source for the beta version of the nitesend wallet is ready, I'm just building a compiler environment for the windows environment. I'm not sure if I can finish it today (it's 3 am here, 'yesterday'), but you will get it tomorrow (eh, today).
It won't be the final version yet, but the essential parts are working, so all who want to test it, can do that.
Biggest missing parts are correct handling of the situations when something can go wrong, ie, if the transaction cannot be completed. However, on these cases, the transaction just won't go throught. On the final version it will roll back and make another try until success.
Also, there is already a server running the nitesend wallet. You can add it to your .conf, ip is 95.85.31.58
|
|
|
|
|
Hi!
Source for the beta version of the nitesend wallet is ready, I'm just building a compiler environment for the windows environment. I'm not sure if I can finish it today (it's 3 am here, 'yesterday'), but you will get it tomorrow (eh, today).
It won't be the final version yet, but the essential parts are working, so all who want to test it, can do that.
Biggest missing parts are correct handling of the situations when something can go wrong, ie, if the transaction cannot be completed. However, on these cases, the transaction just won't go throught. On the final version it will roll back and make another try until success.
Also, there is already a server running the nitesend wallet. You can add it to your .conf, ip is 95.85.31.58
|
|
|
|
Still no answer from MsCollec or Nite about what happens if only one transaction is included in a Nitesend transaction.
If it signs and broadcasts with just a single transaction you lose all anonymity, but still no further explanation from them about how it will work.
You all should consider Nitesend to be vaporware until they can prove otherwise.
Sorry, have been away for a while. It will be configurable, ie you can configure if you want to send it as a single transaction or cancel it. I considering also to make that waiting time as a parameter, long time -> better chances to get a participant. I'v been thinking (and also got a same suggestion) about a possibility to allow some random wallet to participate as a second (or third or fourth) participant to join the transaction. The first nitesend transaction starter might need to send extra 'hiding fee' to get a participant (this might also pose a security risk; is it possible to find out who payed double fee and who recieved it?) . But, then wallet owners might also 'mine' more coins by just allowing their wallet to participate on this hiding process. A community could also help on this; just by agreeing to send coinjoin transactions at the same time they get a better chance to find a participant. |
|
|
|
i STILL want to know how Long takes a confirmation - means in and out  The actual signing route won't usualy take more than a minute or two. Bigger problems is finding another one who wants to make a transaction. |
|
|
|
|
I'm planning to finish a test version next weekend. Depending on the tests with a larger group, first official nitesend release maybe a next day, but up to one week after that, if there are any problems.
The biggest problems are solved, ie the coinjoin transaction is generated, so there is only some details to finish, some polishment to the code and adding security / DoS preventions to the max.
|
|
|
|
So it's trivially identifiable whose outputs are whose based on the observed offers?
I have been wondering that too. Coinjoin itself protects transactions on blockchain only. However it requires someone to log all transactions 24 hours / day. It is one improvement which should be done some day. The offers should be encrypted, so only the participants can decrypt all inputs. Then it would reveal only one address, and that might be generated to be used only once, maybe with 0 output. Other possibility would be to share the offers throught encrypted channel. Any other ideas to improve it? |
|
|
|
Dam whales keeping the price down.
When does the new wallet get released?
I'm planning to finish a test version next weekend. Depending on the tests with a larger group, first official nitesend release maybe a next day, but up to one week after that, if there is some problems. The biggest problems are solved, ie the coinjoin transaction is generated, so there is only some details to finish, some polishment to the code and adding security / DoS preventions to the max. |
|
|
|
To ease your mind, here is also nitesend transaction logs from VootCoin transfer: Nitesend CommitTransaction:
CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
CommitTransaction:
CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet bc92ee60d7 new
WalletUpdateSpent found spent coin 5248.14424298 SUM e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855
NotifyTransactionChanged e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 status=1
NotifyTransactionChanged bc92ee60d786a0f069f9cff884fc500561a7a55c5beb75c9b05068cf6268fc0f status=0
NotifyTransactionChanged e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 status=1
CTxMemPool::accept() : accepted bc92ee60d7 (poolsz 1)
CTxMemPool::accept() : accepted CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
Relaying wtx bc92ee60d7
net.cpp RelayTransaction type = 3
updateWallet e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 1
inWallet=1 inModel=1 Index=7-8 showTransaction=1 derivedStatus=1
updateWallet bc92ee60d786a0f069f9cff884fc500561a7a55c5beb75c9b05068cf6268fc0f 0
inWallet=1 inModel=0 Index=6-6 showTransaction=1 derivedStatus=0
updateWallet e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 1
inWallet=1 inModel=1 Index=8-9 showTransaction=1 derivedStatus=1
received getdata for: ctx bc92ee60d786a0f069f9
Flushing wallet.dat
Flushed wallet.dat 32ms
CTxMemPool::accept() : accepted 7315e8cd86 (poolsz 2)
CTxMemPool::accept() : accepted CTransaction(hash=7315e8cd86, nTime=1403629977, ver=1, vin.size=3, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet 7315e8cd86 new
NotifyTransactionChanged 7315e8cd86261a61e14d7f8896feeee85364a3084d121bb722d4d15d76bdf99d status=0
updateWallet 7315e8cd86261a61e14d7f8896feeee85364a3084d121bb722d4d15d76bdf99d 0
inWallet=1 inModel=0 Index=4-4 showTransaction=1 derivedStatus=0
net.cpp RelayTransaction type = 3
BuildCollectedTransaction : checking CTransaction(hash=7315e8cd86, nTime=1403629977, ver=1, vin.size=3, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
BuildCollectedTransaction : checking CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
BuildCollectedTransaction : generated CTransaction(hash=5f0e386246, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
BuildCollectedTransaction : I have joined this transaction!
BuildCollectedTransaction : Not Signed CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db)
BuildCollectedTransaction : Not Signed CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e)
BuildCollectedTransaction : Not Signed CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082)
BuildCollectedTransaction : Signed CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
BuildCollectedTransaction : signed my part CTransaction(hash=e810a1d3a2, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
Relaying wtx e810a1d3a2
net.cpp RelayTransaction type = 3
received getdata for: ctx e810a1d3a250874e64a9
CTxMemPool::accept() : accepted c68a9805dc (poolsz 1)
CTxMemPool::accept() : accepted CTransaction(hash=c68a9805dc, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=304402201876d7ba350764b8)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=304402206d97cbbd2c759557)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=3045022100e03b72abe17ff0)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet c68a9805dc new
NotifyTransactionChanged c68a9805dce9db80eae070aad85b4a920d45758cafc5e47e4860fd9ca37b381c status=0
net.cpp RelayTransaction type = 1
updateWallet c68a9805dce9db80eae070aad85b4a920d45758cafc5e47e4860fd9ca37b381c 0
inWallet=1 inModel=0 Index=8-8 showTransaction=1 derivedStatus=0
received getdata for: tx c68a9805dce9db80eae0
received getdata for: tx c68a9805dce9db80eae0
received getdata for: tx c68a9805dce9db80eae0
received getdata for: tx c68a9805dce9db80eae0
Flushing wallet.dat
Flushed wallet.dat 25ms
CTxMemPool::accept() : accepted CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet bc92ee60d7 new
NotifyTransactionChanged bc92ee60d786a0f069f9cff884fc500561a7a55c5beb75c9b05068cf6268fc0f status=0
net.cpp RelayTransaction type = 3
updateWallet bc92ee60d786a0f069f9cff884fc500561a7a55c5beb75c9b05068cf6268fc0f 0
inWallet=1 inModel=0 Index=4-4 showTransaction=1 derivedStatus=0
BuildCollectedTransaction : checking CTransaction(hash=bc92ee60d7, nTime=1403629963, ver=1, vin.size=1, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
BuildCollectedTransaction : generated CTransaction(hash=b9f3ace0e4, nTime=1403630563, ver=1, vin.size=1, vout.size=2, nLockTime=0)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402203c473e65bda173e4, nSequence=1105092332)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
Flushing wallet.dat
Flushed wallet.dat 5ms
keypool added key 104, size=101
Nitesend CommitTransaction:
CTransaction(hash=7315e8cd86, nTime=1403629977, ver=1, vin.size=3, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CommitTransaction:
CTransaction(hash=7315e8cd86, nTime=1403629977, ver=1, vin.size=3, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet 7315e8cd86 new
WalletUpdateSpent found spent coin 0.99999 SUM 94ca58603bd8ff52ae8371507a9c512b6b4af9f8b5715ae9dbc6282bae3f7936
NotifyTransactionChanged 94ca58603bd8ff52ae8371507a9c512b6b4af9f8b5715ae9dbc6282bae3f7936 status=1
WalletUpdateSpent found spent coin 1.00 SUM 588c5bd9997aeabfb935e48d0afbdb43e5aa6fd2885d2e4afd05438e06fbb15e
NotifyTransactionChanged 588c5bd9997aeabfb935e48d0afbdb43e5aa6fd2885d2e4afd05438e06fbb15e status=1
WalletUpdateSpent found spent coin 1.00 SUM e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855
NotifyTransactionChanged e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 status=1
NotifyTransactionChanged 7315e8cd86261a61e14d7f8896feeee85364a3084d121bb722d4d15d76bdf99d status=0
NotifyTransactionChanged 94ca58603bd8ff52ae8371507a9c512b6b4af9f8b5715ae9dbc6282bae3f7936 status=1
NotifyTransactionChanged 588c5bd9997aeabfb935e48d0afbdb43e5aa6fd2885d2e4afd05438e06fbb15e status=1
NotifyTransactionChanged e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 status=1
CTxMemPool::accept() : accepted 7315e8cd86 (poolsz 2)
CTxMemPool::accept() : accepted CTransaction(hash=7315e8cd86, nTime=1403629977, ver=1, vin.size=3, vout.size=2, nLockTime=1403630563)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
Relaying wtx 7315e8cd86
net.cpp RelayTransaction type = 3
updateWallet 94ca58603bd8ff52ae8371507a9c512b6b4af9f8b5715ae9dbc6282bae3f7936 1
inWallet=1 inModel=1 Index=3-4 showTransaction=1 derivedStatus=1
updateWallet 588c5bd9997aeabfb935e48d0afbdb43e5aa6fd2885d2e4afd05438e06fbb15e 1
inWallet=1 inModel=1 Index=2-3 showTransaction=1 derivedStatus=1
updateWallet e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 1
inWallet=1 inModel=1 Index=5-6 showTransaction=1 derivedStatus=1
updateWallet 7315e8cd86261a61e14d7f8896feeee85364a3084d121bb722d4d15d76bdf99d 0
inWallet=1 inModel=0 Index=3-3 showTransaction=1 derivedStatus=0
updateWallet 94ca58603bd8ff52ae8371507a9c512b6b4af9f8b5715ae9dbc6282bae3f7936 1
inWallet=1 inModel=1 Index=4-5 showTransaction=1 derivedStatus=1
updateWallet 588c5bd9997aeabfb935e48d0afbdb43e5aa6fd2885d2e4afd05438e06fbb15e 1
inWallet=1 inModel=1 Index=2-3 showTransaction=1 derivedStatus=1
updateWallet e96b43f54799837f627604651da80f28466bd2806d1c98403b51025b6eab6855 1
inWallet=1 inModel=1 Index=6-7 showTransaction=1 derivedStatus=1
received getdata for: ctx 7315e8cd86261a61e14d
CTxMemPool::accept() : accepted e810a1d3a2 (poolsz 1)
CTxMemPool::accept() : accepted CTransaction(hash=e810a1d3a2, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=3045022100e23facd09451db, nSequence=1105092332)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=3044022100e435c1782d891e, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=304402200e025e57b87f6082, nSequence=1105092332)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet e810a1d3a2 new
NotifyTransactionChanged e810a1d3a250874e64a988f6edd9588e0279287ce1a645682cd3b33be44c9168 status=0
updateWallet e810a1d3a250874e64a988f6edd9588e0279287ce1a645682cd3b33be44c9168 0
inWallet=1 inModel=0 Index=6-6 showTransaction=1 derivedStatus=0
net.cpp RelayTransaction type = 3
BuildCollectedTransaction : I have joined this transaction!
BuildCollectedTransaction : Signed CTxIn(COutPoint(94ca58603b, 0), scriptSig=304402201876d7ba350764b8)
BuildCollectedTransaction : Signed CTxIn(COutPoint(588c5bd999, 1), scriptSig=304402206d97cbbd2c759557)
BuildCollectedTransaction : Signed CTxIn(COutPoint(e96b43f547, 1), scriptSig=3045022100e03b72abe17ff0)
BuildCollectedTransaction : VerifyScript passed CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
BuildCollectedTransaction : signed my part CTransaction(hash=c68a9805dc, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=304402201876d7ba350764b8)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=304402206d97cbbd2c759557)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=3045022100e03b72abe17ff0)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
BuildCollectedTransaction : NiteSend transaction is complete, broadcasting.
CTxMemPool::accept() : accepted c68a9805dc (poolsz 1)
CTxMemPool::accept() : accepted CTransaction(hash=c68a9805dc, nTime=1403630563, ver=1, vin.size=4, vout.size=4, nLockTime=0)
CTxIn(COutPoint(94ca58603b, 0), scriptSig=304402201876d7ba350764b8)
CTxIn(COutPoint(588c5bd999, 1), scriptSig=304402206d97cbbd2c759557)
CTxIn(COutPoint(e96b43f547, 1), scriptSig=3045022100e03b72abe17ff0)
CTxIn(COutPoint(e96b43f547, 0), scriptSig=304402204a35d347cdff3d48)
CTxOut(nValue=0.09998, scriptPubKey=OP_DUP OP_HASH160 8f00af5158590a7b49ee943d5844aa2046a85cdf OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=2.90, scriptPubKey=OP_DUP OP_HASH160 64abf1124fd5d650db3e7ce43ee011d2d0dadbf1 OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=5244.14423298, scriptPubKey=OP_DUP OP_HASH160 bb4a6e89de5772de9b050e0988071c491257bb7f OP_EQUALVERIFY OP_CHECKSIG)
CTxOut(nValue=4.00, scriptPubKey=OP_DUP OP_HASH160 4cac0d6698f855ad071a17c7547b7ef2f6442e9b OP_EQUALVERIFY OP_CHECKSIG)
Relaying wtx c68a9805dc
net.cpp RelayTransaction type = 1
http://chainz.cryptoid.info/voot/tx.dws?c68a9805dce9db80eae070aad85b4a920d45758cafc5e47e4860fd9ca37b381c.htm |
|
|
|
|
Show Posts
