AnonyMint
|
|
August 18, 2013, 03:11:56 PM |
|
nope, you can send it over i2p, TOR (to clearnet or HS nodes) and clearnet. the main idea about i2p in anoncoin is to eliminate attacks to find your location and making listening on others connections impossible. (from a technical view) Don't we want miners to be anonymous when they are awarded coins for PoW of the winning block? So then if they use the high-latency setting to be confidently anonymous, they are at a speed disadvantage to those miners who don't want to be anonymous (e.g. the corporations, etc). Also does anyone understand and agree that without high-latency, the NSA knows who you are? (due to timing attacks are possible on low-latency mix-nets) nope, i2p is end to end encrypted, nobody (beside the involved ones) knows what passes from where to where, ie someone else cant see who published it or how high their latency is. Timing attacks work regardless of end-to-end encryption. My understanding is that all low-latency mix-nets are subject to timing attacks. Perhaps you should read up on the research before making a claim? Or am I missing something? Note Tor and I2P are both Chaum mix-nets (so what applies to low-latency attacks of Tor applies also to I2P): https://blog.torproject.org/blog/one-cell-enoughhttp://www.cl.cam.ac.uk/~sjm217/papers/oakland05torta.pdf
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
August 18, 2013, 03:59:39 PM |
|
nope, you can send it over i2p, TOR (to clearnet or HS nodes) and clearnet. the main idea about i2p in anoncoin is to eliminate attacks to find your location and making listening on others connections impossible. (from a technical view) Don't we want miners to be anonymous when they are awarded coins for PoW of the winning block? So then if they use the high-latency setting to be confidently anonymous, they are at a speed disadvantage to those miners who don't want to be anonymous (e.g. the corporations, etc). Also does anyone understand and agree that without high-latency, the NSA knows who you are? (due to timing attacks are possible on low-latency mix-nets) nope, i2p is end to end encrypted, nobody (beside the involved ones) knows what passes from where to where, ie someone else cant see who published it or how high their latency is. Timing attacks work regardless of end-to-end encryption. My understanding is that all low-latency mix-nets are subject to timing attacks. Perhaps you should read up on the research before making a claim? Or am I missing something? Note Tor and I2P are both Chaum mix-nets (so what applies to low-latency attacks of Tor applies also to I2P): https://blog.torproject.org/blog/one-cell-enoughhttp://www.cl.cam.ac.uk/~sjm217/papers/oakland05torta.pdfok, good to see someone with knowledge around here i2p user (A) finds blocks, broadcasts to all users in i2p (UI), now some of the UI are connected to clearnet, some user (B) broadcast it over clearnet to the other nodes, so with a timing attack you could find user B but not user A
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
AnonyMint
|
|
August 18, 2013, 04:11:28 PM |
|
nope, you can send it over i2p, TOR (to clearnet or HS nodes) and clearnet. the main idea about i2p in anoncoin is to eliminate attacks to find your location and making listening on others connections impossible. (from a technical view) Don't we want miners to be anonymous when they are awarded coins for PoW of the winning block? So then if they use the high-latency setting to be confidently anonymous, they are at a speed disadvantage to those miners who don't want to be anonymous (e.g. the corporations, etc). Also does anyone understand and agree that without high-latency, the NSA knows who you are? (due to timing attacks are possible on low-latency mix-nets) nope, i2p is end to end encrypted, nobody (beside the involved ones) knows what passes from where to where, ie someone else cant see who published it or how high their latency is. Timing attacks work regardless of end-to-end encryption. My understanding is that all low-latency mix-nets are subject to timing attacks. Perhaps you should read up on the research before making a claim? Or am I missing something? Note Tor and I2P are both Chaum mix-nets (so what applies to low-latency attacks of Tor applies also to I2P): https://blog.torproject.org/blog/one-cell-enoughhttp://www.cl.cam.ac.uk/~sjm217/papers/oakland05torta.pdfok, good to see someone with knowledge around here i2p user (A) finds blocks, broadcasts to all users in i2p (UI), now some of the UI are connected to clearnet, some user (B) broadcast it over clearnet to the other nodes, so with a timing attack you could find user B but not user A My understanding is that with a timing attack on low-latency mix-nets, you can identify A because you watch the statistical timing of packets throughout the darknet (I2P) to determine where they are originating from by IP address. It is not necessary to know what it is inside the packets. Whereas, with high-latency mix-nets, the peers scramble and delay some packets in random orders and delays, so that the statistical timing attack is foiled.
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
August 18, 2013, 04:20:59 PM |
|
nope, you can send it over i2p, TOR (to clearnet or HS nodes) and clearnet. the main idea about i2p in anoncoin is to eliminate attacks to find your location and making listening on others connections impossible. (from a technical view) Don't we want miners to be anonymous when they are awarded coins for PoW of the winning block? So then if they use the high-latency setting to be confidently anonymous, they are at a speed disadvantage to those miners who don't want to be anonymous (e.g. the corporations, etc). Also does anyone understand and agree that without high-latency, the NSA knows who you are? (due to timing attacks are possible on low-latency mix-nets) nope, i2p is end to end encrypted, nobody (beside the involved ones) knows what passes from where to where, ie someone else cant see who published it or how high their latency is. Timing attacks work regardless of end-to-end encryption. My understanding is that all low-latency mix-nets are subject to timing attacks. Perhaps you should read up on the research before making a claim? Or am I missing something? Note Tor and I2P are both Chaum mix-nets (so what applies to low-latency attacks of Tor applies also to I2P): https://blog.torproject.org/blog/one-cell-enoughhttp://www.cl.cam.ac.uk/~sjm217/papers/oakland05torta.pdfok, good to see someone with knowledge around here i2p user (A) finds blocks, broadcasts to all users in i2p (UI), now some of the UI are connected to clearnet, some user (B) broadcast it over clearnet to the other nodes, so with a timing attack you could find user B but not user A My understanding is that with a timing attack on low-latency mix-nets, you can identify A because you watch the statistical timing of packets throughout the darknet (I2P) to determine where they are originating from by IP address. It is not necessary to know what it is inside the packets. Whereas, with high-latency mix-nets, the peers scramble and delay some packets in random orders and delays, so that the statistical timing attack is foiled. yes, there are delays. more informations which will answer 90% of your questions: http://www.i2p2.de/how_threatmodel.html#timing (i would suggest to read the full threat model). http://www.i2p2.de/techintro.htmlhttp://www.i2p2.de/how_networkcomparisons.htmlif your further interested then this can link you to more info -> http://www.i2p2.de/how.html (the rest of the page also, of course)
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
AnonyMint
|
|
August 18, 2013, 04:44:31 PM |
|
nope, you can send it over i2p, TOR (to clearnet or HS nodes) and clearnet. the main idea about i2p in anoncoin is to eliminate attacks to find your location and making listening on others connections impossible. (from a technical view) Don't we want miners to be anonymous when they are awarded coins for PoW of the winning block? So then if they use the high-latency setting to be confidently anonymous, they are at a speed disadvantage to those miners who don't want to be anonymous (e.g. the corporations, etc). Also does anyone understand and agree that without high-latency, the NSA knows who you are? (due to timing attacks are possible on low-latency mix-nets) nope, i2p is end to end encrypted, nobody (beside the involved ones) knows what passes from where to where, ie someone else cant see who published it or how high their latency is. Timing attacks work regardless of end-to-end encryption. My understanding is that all low-latency mix-nets are subject to timing attacks. Perhaps you should read up on the research before making a claim? Or am I missing something? Note Tor and I2P are both Chaum mix-nets (so what applies to low-latency attacks of Tor applies also to I2P): https://blog.torproject.org/blog/one-cell-enoughhttp://www.cl.cam.ac.uk/~sjm217/papers/oakland05torta.pdfok, good to see someone with knowledge around here i2p user (A) finds blocks, broadcasts to all users in i2p (UI), now some of the UI are connected to clearnet, some user (B) broadcast it over clearnet to the other nodes, so with a timing attack you could find user B but not user A My understanding is that with a timing attack on low-latency mix-nets, you can identify A because you watch the statistical timing of packets throughout the darknet (I2P) to determine where they are originating from by IP address. It is not necessary to know what it is inside the packets. Whereas, with high-latency mix-nets, the peers scramble and delay some packets in random orders and delays, so that the statistical timing attack is foiled. yes, there are delays. more informations which will answer 90% of your questions: http://www.i2p2.de/how_threatmodel.html#timing (i would suggest to read the full threat model). http://www.i2p2.de/techintro.htmlhttp://www.i2p2.de/how_networkcomparisons.htmlif your further interested then this can link you to more info -> http://www.i2p2.de/how.html (the rest of the page also, of course) I read those before coming to this thread. I am trying to warn you that I2P does not have high latency delays yet. It is planned for version 3.0. And without those high-latency delays, the NSA can know who A is. This is not yet an anonymous coin. The I2P one-way paths and (on top of I2P) application protocol delays doesn't protect against the sophisticated timing analysis. The delays must be put into the I2P peers who are relaying the packets.
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
August 18, 2013, 06:21:10 PM |
|
I read those before coming to this thread.
I am trying to warn you that I2P does not have high latency delays yet. It is planned for version 3.0.
And without those high-latency delays, the NSA can know who A is.
This is not yet an anonymous coin.
The I2P one-way paths and (on top of I2P) application protocol delays doesn't protect against the sophisticated timing analysis. The delays must be put into the I2P peers who are relaying the packets.
a truly anonymous coin isnt possible anyway due to the existing blockchain. EDIT: there are also small latencys before relaying the block wich are variable, *coind has to validate a block before it relays it to other nodes, now depending on the speed of pcs, this may differ (tough only in fraction of seconds aslong we dont have blocks with alot of txs). are you interested to hop onto freenode/i2p #anoncoin if you want to submit ideas or just discuss such things? we'r kinda spamming this thread.
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
digeros
|
|
August 18, 2013, 08:29:03 PM |
|
I read those before coming to this thread.
I am trying to warn you that I2P does not have high latency delays yet. It is planned for version 3.0.
And without those high-latency delays, the NSA can know who A is.
This is not yet an anonymous coin.
The I2P one-way paths and (on top of I2P) application protocol delays doesn't protect against the sophisticated timing analysis. The delays must be put into the I2P peers who are relaying the packets.
a truly anonymous coin isnt possible anyway due to the existing blockchain. EDIT: there are also small latencys before relaying the block wich are variable, *coind has to validate a block before it relays it to other nodes, now depending on the speed of pcs, this may differ (tough only in fraction of seconds aslong we dont have blocks with alot of txs). are you interested to hop onto freenode/i2p #anoncoin if you want to submit ideas or just discuss such things? we'r kinda spamming this thread. Well than I guess a Distributed "coinblender" Server system may be of some use to the payment system then??? thoughts???
|
|
|
|
bingjiw
Newbie
Offline
Activity: 37
Merit: 0
|
|
August 18, 2013, 10:19:45 PM |
|
What is the current develop progress status? Is there a time schedule for next releases with new features?
|
|
|
|
AnonyMint
|
|
August 18, 2013, 11:54:16 PM |
|
I read those before coming to this thread.
I am trying to warn you that I2P does not have high latency delays yet. It is planned for version 3.0.
And without those high-latency delays, the NSA can know who A is.
This is not yet an anonymous coin.
The I2P one-way paths and (on top of I2P) application protocol delays doesn't protect against the sophisticated timing analysis. The delays must be put into the I2P peers who are relaying the packets.
a truly anonymous coin isnt possible anyway due to the existing blockchain. EDIT: there are also small latencys before relaying the block wich are variable, *coind has to validate a block before it relays it to other nodes, now depending on the speed of pcs, this may differ (tough only in fraction of seconds aslong we dont have blocks with alot of txs). are you interested to hop onto freenode/i2p #anoncoin if you want to submit ideas or just discuss such things? we'r kinda spamming this thread. I hope the developers are aware of such issues. I don't know how to access "freenode/i2p #anoncoin". Is that an IRC channel?
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
August 19, 2013, 09:34:17 AM Last edit: August 19, 2013, 06:51:55 PM by K1773R |
|
I read those before coming to this thread.
I am trying to warn you that I2P does not have high latency delays yet. It is planned for version 3.0.
And without those high-latency delays, the NSA can know who A is.
This is not yet an anonymous coin.
The I2P one-way paths and (on top of I2P) application protocol delays doesn't protect against the sophisticated timing analysis. The delays must be put into the I2P peers who are relaying the packets.
a truly anonymous coin isnt possible anyway due to the existing blockchain. EDIT: there are also small latencys before relaying the block wich are variable, *coind has to validate a block before it relays it to other nodes, now depending on the speed of pcs, this may differ (tough only in fraction of seconds aslong we dont have blocks with alot of txs). are you interested to hop onto freenode/i2p #anoncoin if you want to submit ideas or just discuss such things? we'r kinda spamming this thread. I hope the developers are aware of such issues. I don't know how to access "freenode/i2p #anoncoin". Is that an IRC channel? yes it is, #anoncoin is accessible with freenode or irc2p (i2p irc) and is relayed between.
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
meeh (OP)
|
|
August 19, 2013, 12:52:41 PM Last edit: August 19, 2013, 02:52:51 PM by meeh |
|
What is the current develop progress status? Is there a time schedule for next releases with new features?
The development status is "in progress". Currently it's the new codebase (from Bitcoin 0.8.3.7) that is under development. Feel free to watch the development here; https://github.com/Anoncoin/anoncoin/tree/master-0.8Release dates are not yet out. We're currently discussing a maybe backport on the IRC seed, with support for Irc2P, or another IRC server inside the I2P network. And maybe a kind of coincontrol in the Qt gui which we are currently looking into. We're aiming on a bigger feature list before another release, since we don't want to spam our users with new small releases to often. Mac OSX users will probably get a early release of the new source once the Qt linking problem is solved. We're currently researching some odd problems where the bundled Qt dylibs requires system libraries that usualy don't exists on OSX installations, which makes the client crash. So that's 1st prio at the moment. (Daemon on OSX is working fine however) I hope the developers are aware of such issues.
Of course we are. Both I, K1773R and BroTroxer have had discussion on this. Implementations of zerocoin, coloredcoin etc have been discussed. And you will probably see one of the features in Anoncoin in the future, and if none of them, another system that's similar and does the same job. No schedule is set on this. However, the latency problem is known, but not addressed yet. Note, none of those features will come in the next release, but probably the next after this. Feel free to join us at #anoncoin (IRC, Freenode or I2P)
|
|
|
|
AnonyMint
|
|
August 20, 2013, 06:28:54 AM |
|
I hope the developers are aware of such issues.
Of course we are. Both I, K1773R and BroTroxer have had discussion on this. Implementations of zerocoin, coloredcoin etc have been discussed. And you will probably see one of the features in Anoncoin in the future, and if none of them, another system that's similar and does the same job. No schedule is set on this. However, the latency problem is known, but not addressed yet. Note, none of those features will come in the next release, but probably the next after this. Feel free to join us at #anoncoin (IRC, Freenode or I2P) Thank you
|
|
|
|
meeh (OP)
|
|
August 20, 2013, 04:03:18 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block!
|
|
|
|
BroTroxer
|
|
August 20, 2013, 04:30:53 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block! With excitement, without problems. Just the way we like it!
|
|
|
|
A L I E N
Legendary
Offline
Activity: 1358
Merit: 1000
|
|
August 20, 2013, 05:15:26 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block! With excitement, without problems. Just the way we like it! Looks like the days of loading up on low diff ANC are over. Its going to be hard to mine now with the difficulty keeping pace with the hash rate. Any idea why CoinChoose is showing a 17.42 block reward?
|
|
|
|
meeh (OP)
|
|
August 20, 2013, 05:28:46 PM |
|
Looks like the days of loading up on low diff ANC are over. Its going to be hard to mine now with the difficulty keeping pace with the hash rate.
Any idea why CoinChoose is showing a 17.42 block reward?
Yepp I guess CC is using old information. PS: If you look at the diff now, don't worry, it will be stable soon.
|
|
|
|
BroTroxer
|
|
August 20, 2013, 10:27:49 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block! With excitement, without problems. Just the way we like it! Looks like the days of loading up on low diff ANC are over. Its going to be hard to mine now with the difficulty keeping pace with the hash rate. Any idea why CoinChoose is showing a 17.42 block reward? Yeah, this way it should be a lot more fair to miners that are mining around the clock, or just often. No more hit 'n runs by the big guys to grab easy coins and mess up the difficulty for others.
|
|
|
|
DiCE1904
Legendary
Offline
Activity: 1118
Merit: 1002
|
|
August 21, 2013, 02:44:44 AM |
|
What is the current develop progress status? Is there a time schedule for next releases with new features?
The development status is "in progress". Currently it's the new codebase (from Bitcoin 0.8.3.7) that is under development. Feel free to watch the development here; https://github.com/Anoncoin/anoncoin/tree/master-0.8Release dates are not yet out. We're currently discussing a maybe backport on the IRC seed, with support for Irc2P, or another IRC server inside the I2P network. And maybe a kind of coincontrol in the Qt gui which we are currently looking into. We're aiming on a bigger feature list before another release, since we don't want to spam our users with new small releases to often. Mac OSX users will probably get a early release of the new source once the Qt linking problem is solved. We're currently researching some odd problems where the bundled Qt dylibs requires system libraries that usualy don't exists on OSX installations, which makes the client crash. So that's 1st prio at the moment. (Daemon on OSX is working fine however) I hope the developers are aware of such issues.
Of course we are. Both I, K1773R and BroTroxer have had discussion on this. Implementations of zerocoin, coloredcoin etc have been discussed. And you will probably see one of the features in Anoncoin in the future, and if none of them, another system that's similar and does the same job. No schedule is set on this. However, the latency problem is known, but not addressed yet. Note, none of those features will come in the next release, but probably the next after this. Feel free to join us at #anoncoin (IRC, Freenode or I2P) Very happy to see you pushing for the mac client update, thank you
|
|
|
|
sal002
|
|
August 21, 2013, 12:49:20 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block! With excitement, without problems. Just the way we like it! Looks like the days of loading up on low diff ANC are over. Its going to be hard to mine now with the difficulty keeping pace with the hash rate. Any idea why CoinChoose is showing a 17.42 block reward? Fixed - not sure why I was but was the reward different in the past?
|
|
|
|
BroTroxer
|
|
August 21, 2013, 03:28:13 PM |
|
Protocol switch complete - Fun watching the coin change diff after each block! With excitement, without problems. Just the way we like it! Looks like the days of loading up on low diff ANC are over. Its going to be hard to mine now with the difficulty keeping pace with the hash rate. Any idea why CoinChoose is showing a 17.42 block reward? Fixed - not sure why I was but was the reward different in the past? The rewards are currently at 5 coins per block. I see CoinChoose still reports it to be 17.42. There was a change made to the coin that reduces block sizes from the original plans, adding rapid dynamic difficulty changes at the same time as block rewards decreases. You can read about the changes in the previous announcement posted here; https://bitcointalk.org/index.php?topic=227287.msg2764735#msg2764735
|
|
|
|
|