Topic: Should Monero run an ICO? - page 4. (Read 7680 times)

I think I'm going to steer clear of this given the devs have known about fatal flaws for two years and have done nothing to fix it.

Thanks for the info.


~BCX~

I discovered 13 ZeroDay's in Monero source code and exploited the v2 block bug that split the network consensus. The remaining 12 I'm keeping in my back pocket so next time they piss me off again or attempt a DoS.

Oh man, ZeroDay and they're using ring sigs? Why, that's just plain stupid especially if they've known about it for two years.


How did they find this out?


~BCX~

Yes it has ZeroDay Vulnerabilities dating back to the Bytecoin fork that still remain. Lastly, it cannot scale; either they drop the ring signatures or their botnet will be mining by itself. I vote no to bailouts (ICO) caused by lack of skilled programmers.

I vote for yes. after all they do have a considerable marketcap already. it would be profitable for the investors as well and monero team can market the coin widely.

IS.


IT.


TRUE?

I wouldn't be so sure about that if I were you.


Didn't Anonymint or someone find a flaw in the code that allowed a person with sufficient hash power to exploit the "untraceable part"


~BCX~

I'll say it again - the Monero ICO is in full swing.  
  
You can get your Monero ICO tokens on any major exchange.  The thing is, you're not buying them from the pockets of some unscrupulous premine scam devs - you are buying them from people who have used computers to do actual mathematical work to generate them: hence proof-of-work.  
  
When you buy a premine ICO, what are you buying?  Smoke and mirrors.  When you buy a Monero token, pre-GUI, pre-awareness phase, pre-everything that is yet to come.... you are still buying a token generated fairly and honestly using the only known consensus mechanism that has ever been shown to actually secure blockchains.  And the best part - you can use it right now for its intended purpose: a secure, untraceable unit of account.  It is the best money that our civilization has ever invented. 
  
And it exists now, and has existed for two years. 
 
The Monero 'ICO' is happening right now under your nose... but it won't last forever.

Please name them. It will help inform those interested in the ICO.

Development halted? When did it ever start?

I haven't looked at this coin since early 2014 and a lot of the same flaws that were there in the beginning are still there.

I'm guessing Anonymint didn't hold Smooth's hand tight enough.

Perhaps that's why Smooth destroyed Anonymint's reputation.


~BCX~

Keeping up with what?

Oh, you mean bitcoin?

looks at all themz issues! And somes of dems r frumz 2015zz!!


Incoming block downloads repeatedly freezing in 0.12 Bug P2P
#7596 opened on Feb 25 by jameshilliard
 8
salvagewallet drops valid keys Bug Wallet
#7379 opened on Jan 19 by MarcoFalke
 3
Bitcoind bad_alloc -> ConnectBlock fail Bug
#7228 opened on Dec 18, 2015 by sipa
 3
Assertion failure in scheduler.cpp after Ctrl-Cing in AppInit2 Bug Priority Low
#6735 opened on Sep 29, 2015 by laanwj
 0
GetTempPath has unchecked error conditions Bug
#6702 opened on Sep 19, 2015 by luke-jr
 2
GetTempPath is insecure Bug
#6701 opened on Sep 19, 2015 by luke-jr
 0
LoadExternalBlockFile is missing locking Bug
#6691 opened on Sep 17, 2015 by morcos
 1
importaddress when walletnotify is set, causes the notification of large number of unrelated transactions Bug Wallet
#6095 opened on May 1, 2015 by eriksank
 14
importprivkey fails when walletnotify is set Bug Wallet
#6084 opened on Apr 29, 2015 by y
 5
Chainstate Corruption: error in middle of Win64 version 0.10.0 Bug Data corruption Windows
#5865 opened on Mar 7, 2015 by VikingNation
 2
Bitcoin Core 0.10 freezing and disconnecting during synchronization Bug GUI P2P UTXO Db and Indexes
#5851 opened on Mar 3, 2015 by MrKrzYch00
 17
Missing cs_main lock in ProcessMessage() Bug P2P
#5678 opened on Jan 19, 2015 by johannes87
 4
bug in DateTimeStrFormat? Bug Priority Low Upstream
#5631 opened on Jan 9, 2015 by Diapolo
 7
libdb_cxx-4.8 leaks? Bug Resource usage
#5380 opened on Nov 26, 2014 by jonasschnelli
 8
Initial connection management Bug Priority Low
#5299 opened on Nov 18, 2014 by 21E14
 4
BIP 70 protocol not prompting user to specify payment amount when `outputs` amount field is 0. Bug GUI
#4908 opened on Sep 13, 2014 by derrend
 2
-whitebind behavior is not properly documented and (IMO) counterintuitive Bug Docs and Output
#4872 opened on Sep 8, 2014 by Michagogo
 0
fee estimates file sanity check too strict Bug TX fees and policy
#4639 opened on Aug 5, 2014 by gavinandresen
 1
AddTimeData will never update nTimeOffset past 199 samples Bug P2P
#4521 opened on Jul 13, 2014 by xenog
 23
getnewaddress return used address Bug Wallet
#4509 opened on Jul 11, 2014 by mgosk
 3
Potential deadlock on {cs_main, pnode->cs_vSend} Bug
#4493 opened on Jul 9, 2014 by ashleyholman
 2
requesting txs that have already been added to the pool Bug P2P
#4461 opened on Jul 3, 2014 by rebroad
 2
-listen has stopped being set to 0 when -connect present Bug Docs and Output
#4433 opened on Jun 28, 2014 by dgenr8
 0
Transactions in TCP FIN packets appear to be ignored Bug P2P Priority Medium
#4432 opened on Jun 27, 2014 by phillipsjk
 10
When issuing bitcoind the `stop` rpc command, it waits forever for existing clients to disconnect Bug RPC/REST/ZMQ
#4235 opened on May 26, 2014 by ryancdotorg


--

yeah when you're essentially recreating a cryptocurrency from scratch people are gonna file issues.

n00bz

Exactly. Basing it on what one guy does in an arbitrary time window is meaningless. Sometimes I pay attention to opening issues and sometimes I don't.

Also, we changed the development process a bit recently (discussed in one of the dev meetings I think) where PRs which don't blatantly break something but raise potential issues are merged after opening an issue rather than holding back the PR. Many of those issues reference a PR or vice versa.

Yes, this was my point. Since it's fact we cannot debate it. Ciao!

I think what john is saying is obvious if you look at the issues in the last 2 months compared to the amount that have been resolved...  issues are being openned at twice the pace of resolution.

yell scam all you want, but Monero is having problems keeping up.

of course you know this smooth you are the one that opened up most of these issues.


17 issues openned since april 1st


boost_serialization_helper.h:108 Exception at [unserialize_obj_from_file], what=unsupported version
#849 opened 12 hours ago by Gingeropolous
 0
bitmonerod not syncing on armv7h: block does not have enough proof of work .... unexpected difficulty
#847 opened 5 days ago by radfish
 4
Tighten up torsocks usage recommendations in README.md
#844 opened 7 days ago by iamsmooth
 0
Need review of restricted/nonrestricted apis
#843 opened 9 days ago by iamsmooth
 5
json_rpc: method getblock returns invalid json
#841 opened 10 days ago by FelixWeis
 1
--p2p-bind-ip not binding outgoing connections to the specified interface when having more than one interface.
#838 opened 12 days ago by osensei
 0
UNBOUND_LIBRARIES error building on Ubuntu 14.04
#836 opened 14 days ago by laanwj
 6
Feature request: bind multiple RPC ports and selectively control access of each
#835 opened 15 days ago by Gingeropolous
 0
GCC 6.1 compilation errors
#834 opened 17 days ago by moneroexamples
 1
Increased CPU usage in latest version
#833 opened 21 days ago by bobfeldbauer
 10
Feature request: daemon functional in push-only mode
#832 opened 23 days ago by Gingeropolous
 1
parse_tx_extra and failed to deserialize extra field
#829 opened 25 days ago by moneroexamples
 3
Simplewallet RPC log error: "failed to deserialize extra field"
#828 opened 26 days ago by bobfeldbauer
 3
add check to make sure arguments of --log-file and --wallet-file are not pointing to the same file
#820 opened 29 days ago by mbg033
 1
Error: refresh failed: unexpected error: boost::thread_resource_error: Resource temporarily unavailable.
#809 opened on Apr 16 by AJIekceu4
 4
Faster wallet refresh when restoring a wallet
#805 opened on Apr 13 by hyc
 0
lto1: fatal error: bytecode stream generated with LTO version 2.2 instead of the expected 4.0 compilation terminated.
#781 opened on Apr 1 by fluffypony
 

7 issues closed since april 1st

connections not limited to node specified in --add-exclusive-node
#848 opened 5 days ago by radfish
 2
restricted rpc modifications
#839 opened 11 days ago by Gingeropolous
 2
pine64 compile error, using "Ubuntu Linux Image base on Longsleep 20160421 image, Pine64" and standard
#830 opened 23 days ago by Gingeropolous
 3
Compile fail, ubuntu 14.04
#807 opened on Apr 16 by Gingeropolous
 3
sweep_unmixable Error: no connection to daemon. Please make sure daemon is running.
#804 opened on Apr 12 by perl5577
 3
save_bc hangs
#802 opened on Apr 6 by moneromooo-monero
 1
Add "outgoing_transfers" as simplewallet json_rpc method.
#795 opened on Apr 5 by micro-machine
 3
Wallet file inconsistencies
#793 opened on Apr 3 by arnuschky
 5
Invalid transactions are somehow reaching the daemon's tx pool resulting in rejected mined blocks.
#792 opened on Apr 3 by osensei
 1
Possible issue with genesis block generation
#790 opened on Apr 3 by tewinget

He is the Many Faced Scammer.  VCash/VanillaCoin/etc isn't long for this world.  He will be back (or already is) with a new scam.
 

More often? There are 2047 commits and 214 issues (combined open and closed)

Get lost scammer

You keep blabbing about some phantom vulnerability.  Please link me to a clear description of this vulnerability so I can read it with no hype.

Monero is creating issues mofe often than they are pushing code: https://github.com/monero-project/bitmonero/issues

Still no attempt from them to fix their remaining ZeroDay vulnerabilities.

That is the reasoin why the Monero price is not rising. The cost to the bonet operator is very low, they will dump at any price.

How dare you compare that crap with something as nice as Bitcoin, dude