|
chaeplin
|
 |
June 13, 2014, 12:44:56 PM |
|
Coin come to xnode = many split transaction in pending at
same time transaction output from xnode using "reservebalance" (coin confirmed ready to transfert not minted) to destination adress = one different transaction
The two transaction are made instantly but not tie.
If you turn off your xnode or computer when input come ,your coin in the reservebalance are already sent and in pending on the network to the destination ! No need to wait for a block or confirmation they are completely separate input and output.
If its the fact that input come in the xnode before to be sent at output , we can tell to the xnode to send coin before taking the coin from the input if not input bounce to another xnode.
Is this your thought ? I should draw a diagram to understand. If orphaned, tx should be out again. |
|
|
|
|
|
|
|
|
|
|
|
"I'm sure that in 20 years there will either be very large transaction volume or no volume." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Queeq
|
|
June 13, 2014, 12:59:50 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
|
|
|
|
|
|
chaeplin
|
|
June 13, 2014, 01:03:57 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
Current design require two tx. Make it to single tx. |
|
|
|
|
|
Queeq
|
|
June 13, 2014, 01:12:05 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
Current design require two tx. Make it to single tx. Why two txs cannot reside in one block? |
|
|
|
|
luigi1111
Legendary
 Offline
Activity: 1105
Merit: 1000
|
|
June 13, 2014, 01:26:17 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
Current design require two tx. Make it to single tx. Why two txs cannot reside in one block? They can, certainly, but how do you make sure two tx's are included in the same block? |
|
|
|
|
|
chaeplin
|
|
June 13, 2014, 01:29:49 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
Current design require two tx. Make it to single tx. Why two txs cannot reside in one block? A ---- mixer ---- B tx1 tx2 There is network delay. Actually A is broadcasting to network his tx, signed by his private key. A commuinate mixer to know which address should be used, mixer issue a address for A, and inform mixer real payee. It should be included in a block. There is possible way, if mixer relay the tx solely. Hold the tx1 and process tx2, broadcast tx1 and tx2 simultaneously. But who generate block ? There is network delay. tx1 and tx2 can be splitted to two blocks sometimes. no 100%. By any means decribed in https://bitcointalk.org/index.php?topic=631052.msg7289855#msg7289855 |
|
|
|
|
adhitthana
Legendary
Offline
Activity: 1190
Merit: 1000
|
|
June 13, 2014, 01:42:51 PM |
|
Thank you Chaeplin
|
|
|
|
|
|
chaeplin
|
|
June 13, 2014, 01:45:46 PM |
|
Thank you Chaeplin
You're welcome. |
|
|
|
|
NewWorldCoiner
Sr. Member
Offline
Activity: 490
Merit: 250
Saved you from a scam? Send me some BTC!
|
|
June 13, 2014, 02:03:20 PM |
|
Thank you Chaeplin
Yeah, long overdue I'm afraid, thanks Chaeplin. REV 1.5 will be released today or tomorrow, can I send you some XC to continue testing? PM me your address. |
|
|
|
|
|
chaeplin
|
|
June 13, 2014, 02:09:26 PM |
|
Thank you Chaeplin
Yeah, long overdue I'm afraid, thanks Chaeplin. REV 1.5 will be released today or tomorrow, can I send you some XC to continue testing? PM me your address. Use your exchange address for testing.  |
|
|
|
|
NewWorldCoiner
Sr. Member
Offline
Activity: 490
Merit: 250
Saved you from a scam? Send me some BTC!
|
|
June 13, 2014, 02:25:01 PM |
|
Thank you Chaeplin
Yeah, long overdue I'm afraid, thanks Chaeplin. REV 1.5 will be released today or tomorrow, can I send you some XC to continue testing? PM me your address. Use your exchange address for testing. I meant for you to test it. I don't have the tech skills you do, I'm just an investor!  |
|
|
|
|
|
tr8kr
|
|
June 13, 2014, 02:26:32 PM |
|
If they were on the same block, xnode would not have lost its coins in case of orphaned block, right? In other words, they both went to wrong fork and once it is detected it could be corrected.
Another question is how to ensure they are on the same block.
Current design require two tx. Make it to single tx. Why two txs cannot reside in one block? A ---- mixer ---- B tx1 tx2 There is network delay. Actually A is broadcasting to network his tx, signed by his private key. A commuinate mixer to know which address should be used, mixer issue a address for A, and inform mixer real payee. It should be included in a block. There is possible way, if mixer relay the tx solely. Hold the tx1 and process tx2, broadcast tx1 and tx2 simultaneously.But who generate block ? There is network delay. tx1 and tx2 can be splitted to two blocks sometimes. no 100%. By any means decribed in https://bitcointalk.org/index.php?topic=631052.msg7289855#msg7289855Coin come to xnode = many split transaction in pending at
same time transaction output from xnode using "reservebalance" (coin confirmed ready to transfert not minted) to destination adress = one different transaction
The two transaction are made instantly but not tie.
If you turn off your xnode or computer when input come ,your coin in the reservebalance are already sent and in pending on the network to the destination ! No need to wait for a block or confirmation they are completely separate input and output.
If its the fact that input come in the xnode before to be sent at output , we can tell to the xnode to send coin before taking the coin from the input if not input bounce to another xnode.
Hold the tx1 and broadcast tx2, if successful broadcast tx1 if not go to another mixer That could be made with 1 or 2 or 8 block away between tx1 and tx2 in this example ? |
|
|
|
|
|
chaeplin
|
|
June 13, 2014, 02:47:57 PM |
|
Hold the tx1 and broadcast tx2, if successful broadcast tx1 if not go to another mixer
That could be made with 1 or 2 or 8 block away between tx1 and tx2 in this example ?
I can't assure what is your point, but there is no pending in network. If a tx is broadcasted, it will be included in a block with priority of fee. Hold the tx1 and broadcast tx2, if successful broadcast tx1
Is this meant spend first then take input ? User can monitor whether tx2 is included in a block(whether real payee is paid). And tx1 is not broadcated yet, user can make a another tx and broadcast it. Send coins to his news address. There is a method to delete unconfirmed tx in wallet. |
|
|
|
|
adhitthana
Legendary
Offline
Activity: 1190
Merit: 1000
|
|
June 13, 2014, 02:54:25 PM |
|
Thank you Chaeplin
You're welcome. I can send you some XC as well, if I have your address |
|
|
|
|
|
JakeThePanda
|
|
June 13, 2014, 08:28:44 PM |
|
I've just completed a test on the multi-path system
Receivers Address --->>>>> XXcJEFKxziaH8trY6DruHx9ap39rnDJbK7 - 0.03 XC's
I am going to put a password zip file online with the details
ATSECURE
Chaeplan - go ahead and run your analysis and let us know what you find or DON'T FIND |
|
|
|
|
|
tat123
|
|
June 13, 2014, 08:32:39 PM |
|
I've just completed a test on the multi-path system
Receivers Address --->>>>> XXcJEFKxziaH8trY6DruHx9ap39rnDJbK7 - 0.03 XC's
I am going to put a password zip file online with the details
ATSECURE
Chaeplan - go ahead and run your analysis and let us know what you find or DON'T FIND Paging Dr Chaeplin... Dr Chaeplin your assistance is required. |
|
|
|
|
|
hashnine
|
|
June 13, 2014, 08:49:04 PM |
|
there are only the serious peoples of the 2 community drk and xc? because the 2 official threads are full of kids, so hell  edit: ya this thread seem very nice. |
Careful XC anonymous coin is a scam
|
|
|
mr_random
Legendary
Offline
Activity: 1288
Merit: 1001
|
|
June 13, 2014, 11:12:53 PM |
|
With XC you have to trust the mixer isn't logging the data and that the mixer won't steal your coins. Giving control of your coins to another entity is just asking for trouble.
Thansk I appreciate your (and others input here) So..with DRK the nodes merely witness the change of ownership and verify it? But with a mixer the coins pass into the mixer (rather than merely being witnessed) and then have to be "allowed" out the other end? Can you expand? 1.Where exactly is the "mixer"? 2.If the source is open, then would that mean coins could not be stolen? 3.The developer of XC stated "mixers don't steal coins".....but you seem to think they can? So how would a mixer steal coins? It's simple. You send coins to a address issued by mixer and mixer has private key of the address issued. so how mixer steal it? isn't the mixer program to mix/forward the coins? from what i understand you think mixer can just keep/steal the coin or perhaps forwards to different address? but how? Shutdown computer, lock wallet, diconnect network, power failure. Mixer program should/will mix/forward the coins. Owner of the mixer is problem.. Do you know that mixer takes input/coins and waits at least 2 ~ 3 more blocks confirmation before forwards the coins. 3.The developer of XC stated "mixers don't steal coins".....but you seem to think they can? So how would a mixer steal coins?
True, People steal coins. DRK is a mixer too and they solve this issue by using signatures which removes the incentive for DRK nodes to steal. We both know that XC can use this same idea to solve the issue too. Funny how you don't mention it though. You pretend well but your ultimate aim is to make XC look bad, not really to "help". |
|
|
|
|
|
illodin
|
|
June 13, 2014, 11:41:00 PM |
|
You pretend well but your ultimate aim is to make XC look bad, not really to "help".
I don't know what his ultimate aim is, but if I had his crypto knowledge I would be quiet and buy enough to run a few nodes and hope XC price skyrockets and then keep stealing a coin here and a coin there hoping no one would notice.  |
|
|
|
|
|
chaeplin
|
|
June 14, 2014, 12:03:14 AM
Last edit: June 14, 2014, 12:43:37 AM by chaeplin |
|
http://bitcoin.stackexchange.com/questions/9077/how-to-get-all-addresses-including-the-change-addresses-from-bitcoindhttps://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_listlistaddressgroupings I used the command listaddressgroupings from the bitcoin-qt console window and it listed all my addresses. I then looked for one of my old send transactions here: https://blockchain.info/And found the change address. It matches one of the addresses in the list. listaddressgroupings version 0.7 Returns all addresses in the wallet and info used for coincontrol.
https://en.bitcoin.it/wiki/Accounts_explainedAccounts and Receiving Addresses
Each account is associated with zero or more receiving addresses, and every receiving address is associated with exactly one account. Coins sent to a receiving address in the wallet are credited to the associated account.
Accounts are associated with receiving addresses by using the getaccountaddress, getnewaddress or setaccount methods.
getaccountaddress will return the same address until coins are received on that address; once coins have been received, it will generate and return a new address.
getnewaddress always generates and returns a new address.
setaccount changes the account associated with an existing address. Coins previously received on that address (if any) will be debited from the previous account's balance and credited to the address' new account. Note that doing so may make the previous account's balance negative.
Use the getaddressesbyaccount method to list all addresses associated with an account.
 https://i.imgur.com/lONBhgH.pnghttps://i.imgur.com/Nbufbte.jpghttps://i.imgur.com/oIT9bRo.pnghttps://i.imgur.com/c3tXLCb.pnghttps://i.imgur.com/t4ds57U.pnguser@sv2:~> x11coind getaddressesbyaccount 123
[
"XPB73cXe3b7xwT9mFkg5ra6eQTL7svngeF",
"XTwXxMBzCiMQA5HpjJnd9C3ZFRxx6ZpiJa"
]
user@sv2:~> x11coind listaddressgroupings | grep XPB73cXe3b7xwT9mFkg5ra6eQTL7svngeF
user@sv2:~> x11coind validateaddress XPB73cXe3b7xwT9mFkg5ra6eQTL7svngeF
{
"isvalid" : true,
"address" : "XPB73cXe3b7xwT9mFkg5ra6eQTL7svngeF",
"ismine" : true,
"isscript" : false,
"pubkey" : "02b0cf98b4ca40e58d30bba0744f76a69f5cfa07cdf413d95511578b119075f142",
"iscompressed" : true,
"account" : "123"
}
user@sv2:~>
user@sv2:~> x11coind listaddressgroupings
[
[
[
"XLw5UT2soGbNAUN5AFuMRJY68cXuc7cdTw",
1.43908000
],
[
"XNtedLHBQwKrsMQHZEPDr9tE1HjWQMiv1R",
0.00000000
],
[
"XGEwdTPxJtKkoqMHKMZsv25TXVAShNg4Ph",
0.00000000
],
[
"XD8r41EhUPYkH7UVv5nY6YWHQgifCQhkQp",
0.00000000
],
[
"XKYM87qGNV1JqxwRXeKM4R3uxzBCtkrADh",
0.00000000
],
[
"XL23D2NbRLJgtfjktGAP85ZYzp54W8e3Wz",
0.00000000
],
[
"XUYk9Qzf34wctNmjmSRnFnS8VLVE3U3Lmy",
0.00000000
],
[
"XKLYHkjkX2dPJs76mzusWMsq2qaU6XBVyh",
0.00000000
],
[
"XaMNa2SfxBfnEPwBti94C9nGHsTdmBGkKy",
0.00000000
],
[
"XEen8Rt5b1HrMsGcDsdYpFo1pdx5rYs9WM",
0.00000000
],
[
"XQUiDtApQu1XrHBuY3b58HtcnzENBShxno",
0.00000000
],
[
"XXBNjCrSo3DRoNGEUL6v9o2H9pKfQp9zSa",
0.00000000
],
[
"XRxBQRhQuHTu9WikQSAPu4vNcyFHySTp6t",
0.00000000
],
[
"XCrM9JvrshoRGFYvCVSpR3qEbeA3vs8fKV",
0.00000000
],
[
"XMJgqNXMjSScXS5a9yTy11FTs7brpSwH9b",
0.00000000
],
[
"XZCF1vRA14EP7a6g3JZaMg1vQVVyY7cGuo",
0.00000000
],
[
"XBd8qTY8QoH8dMfENPYuvzyB4huUWhAWGa",
0.00000000
],
[
"XJsegQfpHcw6SkXDcTf9dqHEP8cwEud8Ve",
0.00000000
],
[
"XZi5Sj2X8U58GrbFrQEpj8VpSeNKeYnFeg",
0.00000000
],
[
"XTejrn7nunVRaCv4N128WCGRwJGYJdyZsQ",
0.00000000
],
[
"XW1jdxAikupsj4ioRdoNH2VM9ihkgo9nit",
0.00000000
],
[
"XKASKGtCgjUmdmA4PxP2BsDP1XUvoiVsWk",
0.00093900
],
[
"XMDDFuadQFGas9Zn8nTMVFFGz9hUc7Jteo",
0.00000000
],
[
"XESZeacGKTvWcVfuz47wvjvdGNVm8zW5BA",
0.00000000
],
[
"XZSdpW5fVbtg8fuz4aToqZgpYVLLiQ9nPC",
0.00007000
],
[
"XRsgwxkDyFti2JS3KNM7A6fXJ2foZhsbBX",
0.00000000
],
[
"XNx6Rqzxi1E1YuXphaUPmeyFDHo3pqSLoF",
0.00000000
],
[
"XGmCiP5Q2h3t1X6U44LqxxNXZ9umjoQcd8",
0.00000000
],
[
"XMUpkk7rE387YU4mzmrsDm8cc54jAmrQFU",
0.00000000
],
[
"XTriYTymxpYMjfvktzZFjxK3nWToa98bwf",
0.00000000
],
[
"XX8Byg6vxRwAf3otgi4xaPGJWsc8keAyhc",
0.00000000
],
[
"XTegezJUWp7J25JRGR25W3wJkGskVQeHNy",
0.00000000
],
[
"XZZ96nkKtzYHydV7zVAgEWyiVsH6PNgGF2",
0.00000000
],
[
"XZbs2X8oYK1UkuQJtajGNRrkRWPvAwtS9T",
0.00000000
],
[
"XSprDafFRUFT2StauUXQm1EzV3FWTnU9mr",
0.00000000
],
[
"XaYKZ6mYciJt4NevMXuHfh7NqmUp9uqKiW",
0.00000000
],
[
"XRv8iYVVNjpHqtFzsxn9EjENkZdJkMA5yq",
0.00000000
],
[
"XGyZFFGATyBrnJynzE9q31k5Dx3EcPNBy9",
0.00000000
],
[
"XQNaC83ybcVPd8a5FycxjqFqF553rfLWfj",
0.00000000,
"test"
],
[
"XEvUefvvEv2R8GTeZouWNGgES81PPSPiHy",
0.00000000
],
[
"XEPeo5zJCgXJm7h6vdjxSMCi8d9aDBucd9",
0.00000000
],
[
"XTwXxMBzCiMQA5HpjJnd9C3ZFRxx6ZpiJa",
0.00000000,
"123"
],
[
"XTu5o7sxrgDMrUVRHdJdzU7RCB6YFai2U4",
0.00000000
],
[
"XaL8F4sBdiWWLAhFa7iTRJSyyKqoot5WmX",
0.00000000
],
[
"XFeSgSo1giU6nyA9S18cYRZYzcDcDiPFwP",
0.00000000
],
[
"XCoPapsod7eVwWpL39WakdGXtsshcDCkqp",
0.00000000
],
[
"XW8CkbSvpuwF1KGeGUfBjoP1egSon1zX28",
0.00000000
],
[
"XVBnfs1HNY3mZ7Fxdmee7K56JwoxHB4N2g",
0.00000000
],
[
"XNwAo2C5xZPGxJmuBsHDZR3hsAuPTbH2sP",
0.00000000
],
[
"XUiyxmxpZkpczkxtS8dwuXdmEphBwv2acA",
0.00000000
],
[
"XUtK1KTwWMQUQhBVzYRqbKi2Lqh5j6WQ2G",
0.00000000
],
[
"XFz3rYhzZMfp1rpP1tKcWM5zwhuGoyXd2z",
0.00000000
],
[
"XUMVwpfRtvPph4YyhjkrJgiiJLUyJBmLvN",
0.00000000
],
[
"XUxLhRhiNDxX1XN44i3PWEnHBErUadUgJS",
0.00000000
],
[
"XYPEP4niYhjo2NfGYxRTn58XxiG1GFVRn2",
0.00000000
],
[
"XDhozCRo5qA9Pp6T5N964Atp1VnjRgfgSp",
0.00000000
],
[
"XWPfmL13e6Rz16frMXkfXACK4eKJC5B3Eq",
0.00000000
],
[
"XT9ror66EH4UeyhmGyuhR8CvisQbVoGvmk",
0.00000000
],
[
"XEYksqcRopq14D6kvPiKfsNvrFbBMVxytC",
0.00000000
],
[
"XLrgCKX1fbds3z12PJZAG9xQaw38nWs5Jw",
0.00000000
],
[
"XLtbJLzVJV6H1DsXVCXnwPACfU5H99KsvU",
0.00000000
],
[
"XNApNzYJxZSQY8nDK2X2SLJAWv7uzpGgy2",
0.00000000
]
]
]
|
|
|
|
|
|
