[Poll] What anonymous coin will succed?

[MR1]

Stealth Coin

[robboman]

Shadowcash, first coin with zero-knowledge implemented.

[Poramin Insom]

Shadowcash, first coin with zero-knowledge implemented.

I though Zerovert is the first coin that implemented Zerocoin, which using cryptographic accumulators and digital commitments with zero-knowledge proofs. Correct me, if I'm wrong.

[robboman]

Shadowcash, first coin with zero-knowledge implemented.

I though Zerovert is the first coin that implemented Zerocoin, which using cryptographic accumulators and digital commitments with zero-knowledge proofs. Correct me, if I'm wrong.

Have not really payed attention to zerovert so you are probably right. Shadowcash does not implement a version of zerocoin zk though.

[cryptobeast]

Stealth Coin

The best coin is Absolutely 100% Stealthcoin.
Best development team ever existed in ctyptoworld. Hondo can achieve anything in cryptoworld, the most intelligent head programmer in cryptoland.

[Come-In-Behind]

Zerocoin is the most impractical anonymity scheme there is....I'd rather use a coin with CoinJoin(Darkcoin), than a coin that has zerocoin, with my top spot awarded to coins using Ring Signatures(Monero).

[BanditryAndLoot]

Stealth Coin

The best coin is Absolutely 100% Stealthcoin.
Best development team ever existed in ctyptoworld. Hondo can achieve anything in cryptoworld, the most intelligent head programmer in cryptoland.

You sound more than a little creepy.

I'm putting you on my ignore list, I'm sorry I just don't think you have anything to contribute here.

[dnaleor]

Voted monero because they provide anonymity at protocol level

[thelonecrouton]

What have the Monero 'developers' actually achieved in the 7 months or whatever since they cloned someone else's code, renamed it, and changed the logo?

[othe]

What have the Monero 'developers' actually achieved in the 7 months or whatever since they cloned someone else's code, renamed it, and changed the logo?

Dear Sir,
Dear Darkcoin Hodler,

Please learn how to use github: https://github.com/monero-project/bitmonero/network
Additionally check out the missives and you may encounter other projects related:
https://github.com/monero-project/urs (https://bitcointalk.org/index.php?topic=768499.0)
https://bitcointalk.org/index.php?topic=768499.0
https://github.com/zone117x/node-cryptonote-pool
https://github.com/monero-project/mininero
https://lab.monero.cc/pubs/MRL-0001.pdf
https://lab.monero.cc/pubs/MRL-0002.pdf
https://lab.monero.cc/pubs/MRL-0003.pdf
http://monero.cc/downloads/whitepaper_review.pdf

Jun 2nd 2014

1.   New Logo + branding pack
2.   Repository redesign
3.   Begin website enhancements
4.   live discussions join us on Freenode: #monero for general chat, #monero-dev
5.   MRO changes to XMR to satisfy ISO 4217

Dev diary

1.   Added missing RPC methods
2.   0.8.8 changes to prevent dust attack on block reward
3.   Begun work on documenting the code and providing architecture overviews
4.   Understanding and examining the cryptonote protocols
5.   POW hashing optimisation to improve syncing times and pool verify times
6.   Lucasjones miner optimisation work


Jun 10th

1.   New feature announced deterministic wallets based on mnemonic seed
2.   XMR listed for voting on Mintpal
3.   RPC based Qt GUI wallet

Dev diary

1.   Further RPC work on simplewallet
2.   Added new seed notes
3.   Further code review and implement Doxygen for commenting and code understanding


Jun 18th

1.   Hit number one on mintpal voting list
2.   Begin peer review cryptonote whitepaper
3.   Initial work done on transaction splitting
4.   GUI wallet a lot of work to be done yet and Monero core issues to be resolved first

Dev diary

1.   TX pool handling fix to address high number of orphans
2.   Auto split is now ready for test


June 27th

1.   XMR added to 2 exchanges BTER and Mintpal
2.   White paper review continues http://monero.cc/downloads/whitepaper_annotated.pdf
3.   Bug fix restoring a deterministic wallet and old transactions
4.   Stabilising Monero, pools, merchants and exchanges
5.   Auto splitting ready for release

Dev diary

1.   Slow_hash huge changes to add AES-NI
2.   Major daemon overhaul in progress; windows support to follow
3.   Simple wallet split to Simplewallet (CLI) and RPCwallet (standalone RPC daemon)


July 6th

1.   CryptoNote peer review continues
2.   Auto splitting is now in the main code base

Dev diary

1.   RPC wallet ready for test


July 13th

1.   GUI’s received and bounties paid. Won’t be directly integrated yet
2.   CryptoNote white paper review is coming to close
3.   Begun work to re-implement the mnemonic word list in other languages

Dev diary

1.   Core major work begin to Implement an embedded database
2.   I2P focus moves from libi2pcpp to i2pd. Focus on persistent connections


July 20th

1.   Begun reviewing the implementation of CryptoNote following the white paper review
2.   Embedded database work in progress the hope is to reduce ram requirements
3.   Information security specialist joins the team
4.   German word list complete now moving onto Portuguese

Dev diary

1.   Abstraction of the blockchain storage functions completing (enabler for performance testing)
2.   Daemonising Monero work is largely completed
3.   RPC wallet can now run multiple instances (where machines need to run multiple wallets)
4.   DNS seed nodes work begun that will later replace hardcoded seed nodes
5.   Exchange’s poll get_payments fix for multiple payment IDs is testing


July 23rd

1.   Monero trading pairs added to Poloniex
2.   BSD 3-clause license changes
3.   README build instructions improved
4.   Developer training for Git usage

Dev diary

1.   RPC enhancements a new Get_info
2.   get_bulk_payments developed and ready


August 3rd

1.   Launched fireside chats
2.   Begun tracking downloads 41,425 in the first 3 recorded weeks from 15/06
3.   XMR pairs rise to 5830 XMR of volume after first 12 days
4.   Monero added to coinSource Trust Index with a score of  6 out of 7 stars
5.   Build process streamlined

Dev diary

1.   Windows build script to simplify windows builds
2.   QOS developed and ready, peripherals to be completed
3.   Embedded database is proving complex, work continues
4.   Issues resolved from logs, blockheight parameter and query_key
5.   DNS seeder code available for review


August 10th

1.   First look at the gui in the first fireside chat was positively received
2.   Monero price ticker released
3.   Test environment secured and ready for continuous integration process

Dev diary

1.   Abstracted BlockchainDB functions coming together
2.   CMakelist overhauled
3.   Unit test review/creation has begun
4.   Planning migration to new servers for blockchain and client download


August 16th

1.   GUI test release available
2.   Monero broke 600 subscribers to our sub-reddit
3.   Open source Monero stratum proxy released
4.   Finalising QoS bandwith control

Dev diary

1.   Mingw64 / msys2 largely complete
2.   Wallet code under refactoring
3.   Abstraction and refactoring Blockchain functions ready for some performance testing
4.   QoS ready awaiting testing and then release


September 15th

1.The Monero Research Lab is an open collective academic group continuing to make papers towards the analysis and improvement of the underlying core
2. Second #Monero-Dev Fireside (Fri September 19th, 2014, at 10:00 EST)
3. Merchandise available http://www.zazzle.com/monerogear* coin team gets 15% commission
4. URS released, a Monero project written in Go that allows you to sign messages using ring signatures as part of a group
5. New tagged release, 0.8.8.4, now available for download
6. GUI work delayed due to addressing some core issues following recent events. Progress continuing
7. Monero added to Coin Swap https://coin-swap.net/market/XMR/BTC

Dev diary

1. Development branch on hold, will be brought back into sync following emergency measures implemented
2. FreeBSD Compatability: Monero now works on FreeBSD out the box
3. New Makefile target, release-static, that builds statically linked binaries for redistribution.
4. Wallet: per-kb fees are nearly complete, and will be deployed to testnet within the next week or so
5. Blockchain: Work delayed by  blockchain attacks. Getting back on track with DB work
6. Core: Devs note, all non-critical "errors" and warnings have been moved to log-level 1


October 6th

1. New official Monero forum. Come find us! @ https://forum.monero.cc
2. Working hard in the background on the codebase
3. Mnemonics system overhauled and added new word lists in Japanese, Portuguese, and Spanish
4. MoneroPulse added; a loosely distributed checkpoint alert system
5. Backup distribution system in place for recovery
6. Research Lab released Research Bulletin, MRL-0003 – around ring signatures
7. Monero now at number 2 on Cryptsy voting list

Dev Diary

1. File check pointing added;  checkpoints are always enforced regular checking
2. DNS check pointing added
3. Working hard on improving the build system so builds are easier and less problematic
4. PoW algorithm annotated in the code and documented by dga


October 13th

1. Back-porting features and fixes added to the current codebase.
2. The GUI is progressing We hope to update the preview binaries in the next week or two
3. per-kb fees in testing. we expect positive testing results
5. Further tweaks to mnemonic system

Dev Diary

1. Further work on build environment ultimately to reduce build issues further down the line
2. Core: documentation continues, with Doxygen comments
3. DNS check pointing and configuration in test
4. mnemonic lists now support a variable trim length


October 20th

1. Focussing on some of the core issues that have been lagging
2. Blockchain database implementation. Lightning Memory-Mapped Database, LMDB ready for limited testing by next week.
3. Additional implementations will be built to compare performance
4. Implementing DNSSEC trust anchors with the assistance of NLnet Labs. it prepares us for more widespread, secure use of the OpenAlias standard
5. Reworking build environment to conform to Kitware recommendations, especially due to poorly implemented CMake in original reference code

Dev Diary

1. Per-kb fee testing is going well on testnet
2. Downloadable RAW blockchain for import your daemon will fully verify the downloaded blockchain
3. Unit tests have been fixed, change is expected to be merged in the next week.
4. Core tests are currently being worked on to bring them up to a 100% working state for regression testing

November 17 - Monero Missives #18 Version 0.8.8.5 delayed because of Windows issues; download binaries from the ANN or the official forum lest you may get bad surprises; MRL (Monero R&D) meetup for improving difficulty retargeting algorithm, simpler and stealthier payment ID, secure use of viewkey during remote access.
November 2 - Monero Missives #17 DB is working, mostly only Linux. Per-kb fee ready to go. New CMake almost ready.
October 27 - Monero Missives #16  has info on the major progress made on the LMDB implementation for blockchainDB, multi-lang wallet format changes, and an update on the CMake work
October 20 - Monero Missives #15 details the overhauling of the CMake build system, an update on the first blockchainDB implementation, and per-kb fee testing

Sorry, we would work faster but we don't have a 50% of coins instamined within 48hours of launch financial advantage like others, nor did we have a fancy IPO or were even around when the coin launched to mine large amounts of it. Oh and we work for free anyway.



May i ask what Darkcoin has archived since the 1 year or whatever after they took the perfectly working Bitcoin source and applied a sheme that gmaxwell invented?

[stealth923]

What have the Monero 'developers' actually achieved in the 7 months or whatever since they cloned someone else's code, renamed it, and changed the logo?

They built a website (http://www.monero.cc/) and on-boarded hero shills to pump. Need to give credit for that.

[thelonecrouton]

LOL, 90% of that list was pure blather.

You've implemented some RPC calls, added checkpointing to try and counter an attack that may or may not exist, because you don't understand your cloned code, and haven't managed to produce an official GUI wallet yet, which would take anyone else about a weekend.

Oh, and argued endlessly about your inflation problem, without actually doing anything about it.

[othe]

Ok - you are too "limited" to use github and check the code out.

Darkcoin is better suited for you and your behaviour anyway. You asked what we did, i gave u a list, but of course you weren't interested in a real answer anyway so you just continue your bullshit talk - as expected.

I asked you what DRK archive within 1 year, please provide also a list.


PS: This attack was pretty real: https://lab.monero.cc/pubs/MRL-0002.pdf ; We didn't add "checkpoints" at the supposed second attack; we added a dns checkpointing system using dnssec - i am sure u don't get the difference, but maybe others are interested.
PS2: I know it makes no sense to try to get ignorant people to read something, but maybe others will.
PS3: You have no idea what it takes to make a useable GUI from the start, else you would have checked the work that was involved in Bitcoin QT: https://github.com/bitcoin/bitcoin/commits/master/src/qt? - which has alone 45 pages of github commits: https://github.com/bitcoin/bitcoin/commits/master/src/qt?page=45 - which is a bit more than a weekend - except for you of course.

[Ignition75]

What have the Monero 'developers' actually achieved in the 7 months or whatever since they cloned someone else's code, renamed it, and changed the logo?

They built a website (http://www.monero.cc/) and on-boarded hero shills to pump. Need to give credit for that.

+1 The constant XMR shills and Hero Account purchasing is getting a wee bit obvious and tiresome.

[BanditryAndLoot]

What have the Monero 'developers' actually achieved in the 7 months or whatever since they cloned someone else's code, renamed it, and changed the logo?

They built a website (http://www.monero.cc/) and on-boarded hero shills to pump. Need to give credit for that.

+1 The constant XMR shills and Hero Account purchasing is getting a wee bit obvious and tiresome.

I'm now watching all three of you, very carefully.

[thelonecrouton]

PS3: You have no idea what it takes to make a useable GUI from the start, else you would have checked the work that was involved in Bitcoin QT: https://github.com/bitcoin/bitcoin/commits/master/src/qt? - which has alone 45 pages of github commits: https://github.com/bitcoin/bitcoin/commits/master/src/qt?page=45 - which is a bit more than a weekend - except for you of course.

Wrapping an existing CLI app in a GUI is trivial. Is there some other reason you haven't done it?

[smooth]

PS3: You have no idea what it takes to make a useable GUI from the start, else you would have checked the work that was involved in Bitcoin QT: https://github.com/bitcoin/bitcoin/commits/master/src/qt? - which has alone 45 pages of github commits: https://github.com/bitcoin/bitcoin/commits/master/src/qt?page=45 - which is a bit more than a weekend - except for you of course.

Wrapping an existing CLI app in a GUI is trivial. Is there some other reason you haven't done it?

That has been done. There are at least two of those that we paid for (at least the team largely paid for them -- there may have been some outside donations to the bounties as well). We have a more ambitious GUI development in progress that is independent of those simpler ones that were done within a month or two.

[rangedriver]

Why is Darkcoin even on this list?

[thelonecrouton]

PS3: You have no idea what it takes to make a useable GUI from the start, else you would have checked the work that was involved in Bitcoin QT: https://github.com/bitcoin/bitcoin/commits/master/src/qt? - which has alone 45 pages of github commits: https://github.com/bitcoin/bitcoin/commits/master/src/qt?page=45 - which is a bit more than a weekend - except for you of course.

Wrapping an existing CLI app in a GUI is trivial. Is there some other reason you haven't done it?

That has been done. There are at least two of those that we paid for (at least the team largely paid for them -- there may have been some outside donations to the bounties as well). We have a more ambitious GUI development in progress that is independent of those simpler ones that were done within a month or two.

Fair enough.

What's the degree of centralisation in mining with Monero? Most PoW coins (Darkcoin is no exception) are horribly vulnerable to a few big pools being taken down or subverted, to the point where calling it a decentralised currency is an outright lie.

Anywhere I can find stats for Monero pools?

Basic blockchain security is a fundamental issue and I have yet to find any coin that addresses it in a credible way. Or even admits the problem, for that matter.

[illodin]

Basic blockchain security is a fundamental issue and I have yet to find any coin that addresses it in a credible way. Or even admits the problem, for that matter.

AnonyMint feels strongly about the issue and also had some ideas about that but he is keeping them to himself for now. He was hinting that the mining should be made unprofitable while at the same time everyone should be able to mine (profitably???). Probably it can't be solved at all, so something else will take over eventually.