MONERO DASH and VNL EXPOSED AS NOT ANON by VERGE CURRENCY (former DogeCoinDark)

[CryptocurrencyNetwork]

well i guess that does it.

monero/dash arent anon because theyre more expensive than some other cryptocoin.

where do i get in line to buy the next one?

To correct you, Verge is too cheap to ignore

[Mig-23]

let's compete honestly

we don't need to dropped each other

[iliasyaco]

well i guess that does it.

monero/dash arent anon because theyre more expensive than some other cryptocoin.

where do i get in line to buy the next one?

To correct you, Verge is too cheap to ignore

you right. I bought them at 9 sat 

[Rotator]

Don't like projects over 100M of total coins. This what i don't like Dogecoin and some others.
This way you one billion of coins can have 1sat and above.
This is forced capitalization with small jump you have even more false feeling of increasing demand for this coin.

[fluffypony]

I think credit must be given where credit is due - it's good that they've built out Tor and I2P versions of Electrum.

I think it's pretty short-sighted that they haven't engaged with the Electrum dev community to add I2P support to Electrum server, which would allow Electrum volunteers who are already running servers on Tor and/or clearnet to add I2P support to their server if they so desire.

I also think that it's largely irrelevant whether the Electrum server knows your IP or not, you're already providing it with so much metadata that grouping your addresses becomes trivial. Who cares if you only ever use Electrum over I2P, but then you go buy a yoyo online and an attacker gets your physical address from that payment (and they can link every transaction you've ever done)?

Another concern that I have is with I2P's router being written in Java. It's not terrible, but the additional dependency (especially one with such a poor track record) is a little frightening. It's also the primary reason why we've been working with members of the I2P community to get C++-based I2P router projects going, which will allow much better and more direct integration. Hopefully Verge will switch to Kovri when we're at a stable and secure release point: https://github.com/monero-project/kovri

Thanks for the detailed input, I agree that an I2P version of Electrum is a nice feature. I have no problems with their developments and didn't have any in the past. The attitude bothers me.

Saw your I2P router project previously, how is it progressing?

Good - we're uncovering lots of stuff-the-spec-says-but-the-implementation-does-differently issues, and it is a COMPLETE pain to secure it, but I think there's a lot of good stuff coming out.

For instance, I2P's reseeding is almost entirely centralised - they have a central maintainer (as in a person) who actively maintains reseed lists!! They're basically unaware of all the stuff that Bitcoin has done on the seeding side, not through ignorance, but because change is hard.

Similarly, they have tons of RNG fallback stuff, but in 2016 the prevailing advice is "use /dev/urandom or CryptGenRandom()". This wasn't true back-in-the-day, but the implementation no longer reflects the environment.

[Dogedarkdev]

I think credit must be given where credit is due - it's good that they've built out Tor and I2P versions of Electrum.

I think it's pretty short-sighted that they haven't engaged with the Electrum dev community to add I2P support to Electrum server, which would allow Electrum volunteers who are already running servers on Tor and/or clearnet to add I2P support to their server if they so desire.

I also think that it's largely irrelevant whether the Electrum server knows your IP or not, you're already providing it with so much metadata that grouping your addresses becomes trivial. Who cares if you only ever use Electrum over I2P, but then you go buy a yoyo online and an attacker gets your physical address from that payment (and they can link every transaction you've ever done)?

Another concern that I have is with I2P's router being written in Java. It's not terrible, but the additional dependency (especially one with such a poor track record) is a little frightening. It's also the primary reason why we've been working with members of the I2P community to get C++-based I2P router projects going, which will allow much better and more direct integration. Hopefully Verge will switch to Kovri when we're at a stable and secure release point: https://github.com/monero-project/kovri

Thanks for the detailed input, I agree that an I2P version of Electrum is a nice feature. I have no problems with their developments and didn't have any in the past. The attitude bothers me.

Saw your I2P router project previously, how is it progressing?

Good - we're uncovering lots of stuff-the-spec-says-but-the-implementation-does-differently issues, and it is a COMPLETE pain to secure it, but I think there's a lot of good stuff coming out.

For instance, I2P's reseeding is almost entirely centralised - they have a central maintainer (as in a person) who actively maintains reseed lists!! They're basically unaware of all the stuff that Bitcoin has done on the seeding side, not through ignorance, but because change is hard.

Similarly, they have tons of RNG fallback stuff, but in 2016 the prevailing advice is "use /dev/urandom or CryptGenRandom()". This wasn't true back-in-the-day, but the implementation no longer reflects the environment.

well, hopefully when you buy that yoyo, its over i2p/tor, as clearnet isnt anon..  somehow kovri completely escaped me. im checking it out now. excellent idea, a cpp version of i2p.. at first i was going to make our qt wallets run on i2p via sam, but with i2p updating so often i thought this would be a foolish move. this does look promising, and i now have new plans for tonight.

edit: yeah this kovri project looks great fluffypony, and i see some of the i2p folks are helping out on it, im excited to play with it

[CryptoRekt]

I think credit must be given where credit is due - it's good that they've built out Tor and I2P versions of Electrum.

I think it's pretty short-sighted that they haven't engaged with the Electrum dev community to add I2P support to Electrum server, which would allow Electrum volunteers who are already running servers on Tor and/or clearnet to add I2P support to their server if they so desire.

I also think that it's largely irrelevant whether the Electrum server knows your IP or not, you're already providing it with so much metadata that grouping your addresses becomes trivial. Who cares if you only ever use Electrum over I2P, but then you go buy a yoyo online and an attacker gets your physical address from that payment (and they can link every transaction you've ever done)?

Another concern that I have is with I2P's router being written in Java. It's not terrible, but the additional dependency (especially one with such a poor track record) is a little frightening. It's also the primary reason why we've been working with members of the I2P community to get C++-based I2P router projects going, which will allow much better and more direct integration. Hopefully Verge will switch to Kovri when we're at a stable and secure release point: https://github.com/monero-project/kovri

Thanks for the detailed input, I agree that an I2P version of Electrum is a nice feature. I have no problems with their developments and didn't have any in the past. The attitude bothers me.

Saw your I2P router project previously, how is it progressing?

Good - we're uncovering lots of stuff-the-spec-says-but-the-implementation-does-differently issues, and it is a COMPLETE pain to secure it, but I think there's a lot of good stuff coming out.

For instance, I2P's reseeding is almost entirely centralised - they have a central maintainer (as in a person) who actively maintains reseed lists!! They're basically unaware of all the stuff that Bitcoin has done on the seeding side, not through ignorance, but because change is hard.

Similarly, they have tons of RNG fallback stuff, but in 2016 the prevailing advice is "use /dev/urandom or CryptGenRandom()". This wasn't true back-in-the-day, but the implementation no longer reflects the environment.

well, hopefully when you buy that yoyo, its over i2p/tor, as clearnet isnt anon..  somehow kovri completely escaped me. im checking it out now. excellent idea, a cpp version of i2p.. at first i was going to make our qt wallets run on i2p via sam, but with i2p updating so often i thought this would be a foolish move. this does look promising, and i now have new plans for tonight.

edit: yeah this kovri project looks great fluffypony, and i see some of the i2p folks are helping out on it, im excited to play with it

Isn't it funny how a slam thread turned into a beautiful ending? Hillarious.

[meme magic]

aw

[CryptocurrencyNetwork]

I think credit must be given where credit is due - it's good that they've built out Tor and I2P versions of Electrum.

I think it's pretty short-sighted that they haven't engaged with the Electrum dev community to add I2P support to Electrum server, which would allow Electrum volunteers who are already running servers on Tor and/or clearnet to add I2P support to their server if they so desire.

I also think that it's largely irrelevant whether the Electrum server knows your IP or not, you're already providing it with so much metadata that grouping your addresses becomes trivial. Who cares if you only ever use Electrum over I2P, but then you go buy a yoyo online and an attacker gets your physical address from that payment (and they can link every transaction you've ever done)?

Another concern that I have is with I2P's router being written in Java. It's not terrible, but the additional dependency (especially one with such a poor track record) is a little frightening. It's also the primary reason why we've been working with members of the I2P community to get C++-based I2P router projects going, which will allow much better and more direct integration. Hopefully Verge will switch to Kovri when we're at a stable and secure release point: https://github.com/monero-project/kovri

Thanks for the detailed input, I agree that an I2P version of Electrum is a nice feature. I have no problems with their developments and didn't have any in the past. The attitude bothers me.

Saw your I2P router project previously, how is it progressing?

Good - we're uncovering lots of stuff-the-spec-says-but-the-implementation-does-differently issues, and it is a COMPLETE pain to secure it, but I think there's a lot of good stuff coming out.

For instance, I2P's reseeding is almost entirely centralised - they have a central maintainer (as in a person) who actively maintains reseed lists!! They're basically unaware of all the stuff that Bitcoin has done on the seeding side, not through ignorance, but because change is hard.

Similarly, they have tons of RNG fallback stuff, but in 2016 the prevailing advice is "use /dev/urandom or CryptGenRandom()". This wasn't true back-in-the-day, but the implementation no longer reflects the environment.

well, hopefully when you buy that yoyo, its over i2p/tor, as clearnet isnt anon..  somehow kovri completely escaped me. im checking it out now. excellent idea, a cpp version of i2p.. at first i was going to make our qt wallets run on i2p via sam, but with i2p updating so often i thought this would be a foolish move. this does look promising, and i now have new plans for tonight.

edit: yeah this kovri project looks great fluffypony, and i see some of the i2p folks are helping out on it, im excited to play with it

Dev told community to pull up their socks and stop the attacks. Hopefully we can all work together for the greater benefit for the whole community.

If anyone has any non attacking tweets (if you use twitter) include @CryptoOz for a RT.

Forward on, full steam ahead!

[CryptoRekt]

I think credit must be given where credit is due - it's good that they've built out Tor and I2P versions of Electrum.

I think it's pretty short-sighted that they haven't engaged with the Electrum dev community to add I2P support to Electrum server, which would allow Electrum volunteers who are already running servers on Tor and/or clearnet to add I2P support to their server if they so desire.

I also think that it's largely irrelevant whether the Electrum server knows your IP or not, you're already providing it with so much metadata that grouping your addresses becomes trivial. Who cares if you only ever use Electrum over I2P, but then you go buy a yoyo online and an attacker gets your physical address from that payment (and they can link every transaction you've ever done)?

Another concern that I have is with I2P's router being written in Java. It's not terrible, but the additional dependency (especially one with such a poor track record) is a little frightening. It's also the primary reason why we've been working with members of the I2P community to get C++-based I2P router projects going, which will allow much better and more direct integration. Hopefully Verge will switch to Kovri when we're at a stable and secure release point: https://github.com/monero-project/kovri

Thanks for the detailed input, I agree that an I2P version of Electrum is a nice feature. I have no problems with their developments and didn't have any in the past. The attitude bothers me.

Saw your I2P router project previously, how is it progressing?

Good - we're uncovering lots of stuff-the-spec-says-but-the-implementation-does-differently issues, and it is a COMPLETE pain to secure it, but I think there's a lot of good stuff coming out.

For instance, I2P's reseeding is almost entirely centralised - they have a central maintainer (as in a person) who actively maintains reseed lists!! They're basically unaware of all the stuff that Bitcoin has done on the seeding side, not through ignorance, but because change is hard.

Similarly, they have tons of RNG fallback stuff, but in 2016 the prevailing advice is "use /dev/urandom or CryptGenRandom()". This wasn't true back-in-the-day, but the implementation no longer reflects the environment.

well, hopefully when you buy that yoyo, its over i2p/tor, as clearnet isnt anon..  somehow kovri completely escaped me. im checking it out now. excellent idea, a cpp version of i2p.. at first i was going to make our qt wallets run on i2p via sam, but with i2p updating so often i thought this would be a foolish move. this does look promising, and i now have new plans for tonight.

edit: yeah this kovri project looks great fluffypony, and i see some of the i2p folks are helping out on it, im excited to play with it

Dev told community to pull up their socks and stop the attacks. Hopefully we can all work together for the greater benefit for the whole community.

If anyone has any non attacking tweets (if you use twitter) include @CryptoOz for a RT.

Forward on, full steam ahead!

From here forward i will no longer be posting direct questions towards other currencies. I will get on the bandwagon of working together to help make a positive impact on the crypto world.

Cheers-
Rekt

[ttookk]

Nice ending.
Faith in the internet restored.

[Mig-23]

Don't like projects over 100M of total coins. This what i don't like Dogecoin and some others.
This way you one billion of coins can have 1sat and above.
This is forced capitalization with small jump you have even more false feeling of increasing demand for this coin.

all depending the spread of the coins

a lot of crypto that only have a little in total coins but the price stuck and can't moving

[traumschiff]

We have talked with the developer in a PM and sorted out everything. Closing the thread.

The problem was never with him tbh, but with the trolls who attack without being clear on what the different features of different projects are trying to accomplish. Apples to oranges.