Official Anoncoin chat thread (including history) - page 75.

matthewh3

legendary

Activity: 1372

Merit: 1003

Quote from: stopthecensors on October 22, 2014, 02:44:01 PM

At this point it looks like the 'cryptsy problem' was actually the 'anc problem'. Now k1ll3r or however the little retard spells his name will keep coming up with excuses or lame fixes.

Anoncoin was a good coin. It has been sabotaged from within by its own devs.

There are lots of highly competent groups working on anonymous coins and yet anc devs cling to the broken zerocoin that will deliver nothing even if it works as intended. Of course there are a legion of shills repeating endlessly 'hurrah for anc, its trustless, read the wiki' etc etc

fucking bunch of conmen

‘Internet Trolls’ Are Actually Jerks in Real Life Too, According to Study

stopthecensors

newbie

Activity: 5

Merit: 0

At this point it looks like the 'cryptsy problem' was actually the 'anc problem'. Now k1ll3r or however the little retard spells his name will keep coming up with excuses or lame fixes.

Anoncoin was a good coin. It has been sabotaged from within by its own devs.

There are lots of highly competent groups working on anonymous coins and yet anc devs cling to the broken zerocoin that will deliver nothing even if it works as intended. Of course there are a legion of shills repeating endlessly 'hurrah for anc, its trustless, read the wiki' etc etc

fucking bunch of conmen

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

Quote from: dotatbg on October 22, 2014, 03:45:47 AM

Quote from: K1773R on October 21, 2014, 11:04:15 AM

Quote from: dotatbg on October 21, 2014, 03:00:06 AM

Quote from: entertheabyss on October 20, 2014, 09:26:40 PM

2) Non standard transactions being propagated by Cryptsy. These transaction are more 100kb in size. By default anoncoin clients do not send out transaction of these size and standard miners do not accept them. Cryptsy has refused to acknowledge that they are doing anything wrong.

And then what? Coins will stay in then middle of nowhere forever?
Cryptsy said

Quote

The transaction does not need to be resent as it is a valid transaction.

but you told non standard transaction. I thing you should patch anoncoin client asap because when this "non standard transaction" has valid txID and in that case it's a valid and should be send and confirmed.

nope, see my post above.
its not about having a "valid" txID nor anything like this. the problems lies in creating too big transactions. seems they managed to even lower the fee more which resulted in failure of tx broadcast (there is a limit).

How can you be sure about too long transactions? They still refuse all requests to post a raw transaction from his mempool. The only thing we know is "Cryptsy do not broadcast some kind of transactions" The right way IMHO:
- Cryptsy post a stuck raw transaction and all we will see what is going on.
- Update your client to broadcast any transaction without limit, or reasonable one.

If his API really use sendtoaddress the problem with too big transactions is your I mean in anc node soft

the mintxfee is designed to disallow spam txs, otherwise every node would have to process those and store it in their mempool, ie a simple DoS vector
this is not anc specific, its in any coin forked from bitcoin (unless its a really old codebase).

if you have a stuck TX, send me the output of getrawtransaction and i'l put it into my node(s), as im a main I2P/TOR/clearnet gateway/node, the tx will be broadcasted successfully and everyone can mine it, unless its violating mintxfee rules and then i can only mine it myself.

TheKoziTwo

legendary

Activity: 1552

Merit: 1047

Can cryptsy please open deposits, or at least add those that are currently pending? The problem is with withdraw, so why close deposits?

mullick

legendary

Activity: 1064

Merit: 1002

Quote from: ?? on ??

Quote from: dotatbg on October 22, 2014, 03:59:52 AM

Quote from: mullick on October 21, 2014, 03:31:21 PM

Quote from: K1773R on October 21, 2014, 12:07:37 PM

Craptsy is now refusing to do anything to get their stuck TX's resolved:

Code:

K1773R: craptsy responded upon the request to give raw transaction to me (they had closed ticket) by their usual rambling about fixing this issue with anoncoin devs
damn its worse than before they dont even broadcast nor are willing to give raw transaction now
yoyo: you see! they refuse to do anything

They refuse to give me/us the transactions and refuse (no idea if its with intent) to broadcast the TX.
Therefore, all TX created by craptsy for ANC cannot be mined unless they change this again.

We had enough problems with Craptsy, this shows just another case of them refusing to follow the protocol or care about its customers. Please stay away for your own sake.

I received the first request for a raw transaction today. To say I have done nothing to remedy the situation is a blatant lie as I was cooperating in pm with you and the other developers.

In no way are we refusing to "Follow the protocol" We run an unmodified anoncoind and send all transactions via "sendtoaddress". Out of the 236 currencies we list. ANC is the only one with this issue

You can say its a cryptsy issue all you want. But anyone that reads the facts can see that is not the case

So you can prove it very easy. Just post a non broadcast or stuck raw transaction

Because in my test node no pending withdraw transaction with ID from my Cryptsy account

This is because anoncoind didn't relay a transaction it created following its own parameters. What is your username and/or txid

Found your username from the chatbox

Code:

anoncoind gettransaction 013a84aeedfefff1c2ea0705ca52b0cedbb588ef2477aca3c7d392ee91cae0cc
{
"amount" : -582.69332273,
"fee" : -0.01000000,
"confirmations" : 0,
"txid" : "013a84aeedfefff1c2ea0705ca52b0cedbb588ef2477aca3c7d392ee91cae0cc",
"time" : 1413774007,
"timereceived" : 1413774007,
"details" : [
{
"account" : "",
"address" : "ANb2Xr919ETN13pp44o69m7t2ZxBMxy7tQ",
"category" : "send",
"amount" : -582.69332273,
"fee" : -0.01000000
}
]
}

anoncoind getrawtransaction 013a84aeedfefff1c2ea0705ca52b0cedbb588ef2477aca3c7d392ee91cae0cc
010000000478148200abb929c85fde0454ac76879c8cae7331be12237f527a7516bf55a375000000008b483045022034d4c156478688803e3f9f14b3c7952b91c67214c15e60cb15566ea0dce1b1da022100f7a94d8b96de2b2ea4bf50863cc60e2939ce680d58668d9ac15f3d1eca6d906c014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49ffffffff8972934380de3351240fc14a4a1137d9f8a9f60d883a5959c560a493297f8050000000008a4730440220363b69b1f11a90d5cfec987237246abb2d1cad3758919e838b2181b1fd661ca602205c482c7f571ab1b1ecc79884190dbf4bd30c49ccbd20063c6c2585ef17d3778f014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49ffffffffb83abe1dd6689e8a426c9f09d4ad3b44cd62841f6b3226397e55fa5d2ee4e7f8010000006b48304502207796b265619ce114f266a4f4416ebde116a9cdf5a94ce99ceb566844d82f7463022100c79f555f2aa70ab5827ec5fec82bd9e55f7c46b3851df209314708d85c50d418012103f8384ecfab2fb417a1242914b0c46469d14bf3d5b42a12f8ae6205449256891effffffff547207f7965f51c889fc80f674a147782ef97c03441d5d72c4784880869d2d34000000008c493046022100a43aa751aab71d859fb5964bab695f8100e77a3f6218f15343c54ebad9bf0a4d022100e482bb7207ec59d42d69f4c8e3d94e268e0e42c924e4af336a292eb82d30630d01410437c9fc3e3437143ef7291ad3bda08287c340615ca45fe142a36fef822239dbcac70ae8ad33742be7346c4b4beb7327461034ce1c6aca54e094e71882f2d6eb98ffffffff0231731f910d0000001976a9144abbb8d5f4e799aa1bf25e1b3a419d17a2d0e40188ac98420f00000000001976a91412ea7269cc523fcbaaf5ee8416c3b21b58cddbe488ac00000000

anoncoind decoderawtransaction 010000000478148200abb929c85fde0454ac76879c8cae7331be12237f527a7516bf55a375000000008b483045022034d4c156478688803e3f9f14b3c7952b91c67214c15e60cb15566ea0dce1b1da022100f7a94d8b96de2b2ea4bf50863cc60e2939ce680d58668d9ac15f3d1eca6d906c014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49ffffffff8972934380de3351240fc14a4a1137d9f8a9f60d883a5959c560a493297f8050000000008a4730440220363b69b1f11a90d5cfec987237246abb2d1cad3758919e838b2181b1fd661ca602205c482c7f571ab1b1ecc79884190dbf4bd30c49ccbd20063c6c2585ef17d3778f014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49ffffffffb83abe1dd6689e8a426c9f09d4ad3b44cd62841f6b3226397e55fa5d2ee4e7f8010000006b48304502207796b265619ce114f266a4f4416ebde116a9cdf5a94ce99ceb566844d82f7463022100c79f555f2aa70ab5827ec5fec82bd9e55f7c46b3851df209314708d85c50d418012103f8384ecfab2fb417a1242914b0c46469d14bf3d5b42a12f8ae6205449256891effffffff547207f7965f51c889fc80f674a147782ef97c03441d5d72c4784880869d2d34000000008c493046022100a43aa751aab71d859fb5964bab695f8100e77a3f6218f15343c54ebad9bf0a4d022100e482bb7207ec59d42d69f4c8e3d94e268e0e42c924e4af336a292eb82d30630d01410437c9fc3e3437143ef7291ad3bda08287c340615ca45fe142a36fef822239dbcac70ae8ad33742be7346c4b4beb7327461034ce1c6aca54e094e71882f2d6eb98ffffffff0231731f910d0000001976a9144abbb8d5f4e799aa1bf25e1b3a419d17a2d0e40188ac98420f00000000001976a91412ea7269cc523fcbaaf5ee8416c3b21b58cddbe488ac00000000
{
"txid" : "013a84aeedfefff1c2ea0705ca52b0cedbb588ef2477aca3c7d392ee91cae0cc",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "75a355bf16757a527f2312be3173ae8c9c8776ac5404de5fc829b9ab00821478",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022034d4c156478688803e3f9f14b3c7952b91c67214c15e60cb15566ea0dce1b1da022100f7a94d8b96de2b2ea4bf50863cc60e2939ce680d58668d9ac15f3d1eca6d906c01 04ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49",
"hex" : "483045022034d4c156478688803e3f9f14b3c7952b91c67214c15e60cb15566ea0dce1b1da022100f7a94d8b96de2b2ea4bf50863cc60e2939ce680d58668d9ac15f3d1eca6d906c014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49"
},
"sequence" : 4294967295
},
{
"txid" : "50807f2993a460c559593a880df6a9f8d937114a4ac10f245133de8043937289",
"vout" : 0,
"scriptSig" : {
"asm" : "30440220363b69b1f11a90d5cfec987237246abb2d1cad3758919e838b2181b1fd661ca602205c482c7f571ab1b1ecc79884190dbf4bd30c49ccbd20063c6c2585ef17d3778f01 04ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49",
"hex" : "4730440220363b69b1f11a90d5cfec987237246abb2d1cad3758919e838b2181b1fd661ca602205c482c7f571ab1b1ecc79884190dbf4bd30c49ccbd20063c6c2585ef17d3778f014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49"
},
"sequence" : 4294967295
},
{
"txid" : "f8e7e42e5dfa557e3926326b1f8462cd443badd4099f6c428a9e68d61dbe3ab8",
"vout" : 1,
"scriptSig" : {
"asm" : "304502207796b265619ce114f266a4f4416ebde116a9cdf5a94ce99ceb566844d82f7463022100c79f555f2aa70ab5827ec5fec82bd9e55f7c46b3851df209314708d85c50d41801 03f8384ecfab2fb417a1242914b0c46469d14bf3d5b42a12f8ae6205449256891e",
"hex" : "48304502207796b265619ce114f266a4f4416ebde116a9cdf5a94ce99ceb566844d82f7463022100c79f555f2aa70ab5827ec5fec82bd9e55f7c46b3851df209314708d85c50d418012103f8384ecfab2fb417a1242914b0c46469d14bf3d5b42a12f8ae6205449256891e"
},
"sequence" : 4294967295
},
{
"txid" : "342d9d86804878c4725d1d44037cf92e7847a174f680fc89c8515f96f7077254",
"vout" : 0,
"scriptSig" : {
"asm" : "3046022100a43aa751aab71d859fb5964bab695f8100e77a3f6218f15343c54ebad9bf0a4d022100e482bb7207ec59d42d69f4c8e3d94e268e0e42c924e4af336a292eb82d30630d01 0437c9fc3e3437143ef7291ad3bda08287c340615ca45fe142a36fef822239dbcac70ae8ad33742be7346c4b4beb7327461034ce1c6aca54e094e71882f2d6eb98",
"hex" : "493046022100a43aa751aab71d859fb5964bab695f8100e77a3f6218f15343c54ebad9bf0a4d022100e482bb7207ec59d42d69f4c8e3d94e268e0e42c924e4af336a292eb82d30630d01410437c9fc3e3437143ef7291ad3bda08287c340615ca45fe142a36fef822239dbcac70ae8ad33742be7346c4b4beb7327461034ce1c6aca54e094e71882f2d6eb98"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 582.69332273,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 4abbb8d5f4e799aa1bf25e1b3a419d17a2d0e401 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a9144abbb8d5f4e799aa1bf25e1b3a419d17a2d0e40188ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"ANb2Xr919ETN13pp44o69m7t2ZxBMxy7tQ"
]
}
},
{
"value" : 0.01000088,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 12ea7269cc523fcbaaf5ee8416c3b21b58cddbe4 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a91412ea7269cc523fcbaaf5ee8416c3b21b58cddbe488ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"AHVtfcJ3AgJuDUAVeRfFtew7RBAo2mtwdo"
]
}
}
]
}

mullick

legendary

Activity: 1064

Merit: 1002

Quote from: pebody on October 22, 2014, 05:56:57 AM

withdraw from cryptsy 2014-10-20 11:08:06 106.95742694 ANC
TrxID: 897695f63ef4752ca3848d978759dfec749ba770edb7274f6adb60328f212437
to address ANj92t5i1G5dE3otujPsqwbNBuS2t4dNia

and still nothing... Sad

Code:

anoncoind decoderawtransaction 01000000030823346b430f10920aeeb389db13f37e2430813cd4befbff8b6ad5e4c193b84e000000008b483045022100d99ee867c398bff2382152df5a62994cf96267b5a8e13727c2a15df88e4639df0220507d41cb87f79f5506869250f17ecf4a9dbeedfc6edbcd95778420ba6673eef1014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49ffffffff2eb910df5e4030886f7eb3220a60cbe222de336a85c070951d036fe62efc1190010000008c4930460221008793277f542e69777fc802de2a675781df81ce584f6e7f014c795176c81b82b60221008b4f4e435864d3d1afe0b9e6904e3ba82e27a2d9cadf312c11d277640211a482014104567de27a22ddac4e57d19730bc46cde847c44fe1d33503c61316ea17077793b6c96f7538af5489c2f563d44075bd570de8592caa42ecf8285f05f72b065a4452ffffffff8cc57512b9dba7db64a3172e424d6d29486d812028c74014479fc1fbcea9819b000000008b48304502206d8b39ae4660df5b5ccbc93ef96bc64480447451ae2df33305b3fd0dc9492ca7022100d4bdb7dc6d6cfcddcc33ef44df0112a93fef977efacecab9268ffbcd506655e30141042f2758146f378adaf46d36680053d6ded477c6f0945820bb914220b824148c107a72609e715b6de23f0c73e8750e12ed2b5c8aa1488a18b2719310f8779e2d30ffffffff025c560f00000000001976a914c31c94ecd10f61d5b9edd92a1078cc0f2012409988ac264e567d020000001976a9144c4479e2de1e73aa0db99756c6fd6afe1520c99d88ac00000000
{
"txid" : "897695f63ef4752ca3848d978759dfec749ba770edb7274f6adb60328f212437",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "4eb893c1e4d56a8bfffbbed43c8130247ef313db89b3ee0a92100f436b342308",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100d99ee867c398bff2382152df5a62994cf96267b5a8e13727c2a15df88e4639df0220507d41cb87f79f5506869250f17ecf4a9dbeedfc6edbcd95778420ba6673eef101 04ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49",
"hex" : "483045022100d99ee867c398bff2382152df5a62994cf96267b5a8e13727c2a15df88e4639df0220507d41cb87f79f5506869250f17ecf4a9dbeedfc6edbcd95778420ba6673eef1014104ce87a623acf0512051a94f79a2f4ca051c0276eef40eedbd415a6ff27abc1c34919f8ff564392b9afda266119a2599189b94aee0ec877904d51e5b7b4ba12e49"
},
"sequence" : 4294967295
},
{
"txid" : "9011fc2ee66f031d9570c0856a33de22e2cb600a22b37e6f8830405edf10b92e",
"vout" : 1,
"scriptSig" : {
"asm" : "30460221008793277f542e69777fc802de2a675781df81ce584f6e7f014c795176c81b82b60221008b4f4e435864d3d1afe0b9e6904e3ba82e27a2d9cadf312c11d277640211a48201 04567de27a22ddac4e57d19730bc46cde847c44fe1d33503c61316ea17077793b6c96f7538af5489c2f563d44075bd570de8592caa42ecf8285f05f72b065a4452",
"hex" : "4930460221008793277f542e69777fc802de2a675781df81ce584f6e7f014c795176c81b82b60221008b4f4e435864d3d1afe0b9e6904e3ba82e27a2d9cadf312c11d277640211a482014104567de27a22ddac4e57d19730bc46cde847c44fe1d33503c61316ea17077793b6c96f7538af5489c2f563d44075bd570de8592caa42ecf8285f05f72b065a4452"
},
"sequence" : 4294967295
},
{
"txid" : "9b81a9cefbc19f471440c72820816d48296d4d422e17a364dba7dbb91275c58c",
"vout" : 0,
"scriptSig" : {
"asm" : "304502206d8b39ae4660df5b5ccbc93ef96bc64480447451ae2df33305b3fd0dc9492ca7022100d4bdb7dc6d6cfcddcc33ef44df0112a93fef977efacecab9268ffbcd506655e301 042f2758146f378adaf46d36680053d6ded477c6f0945820bb914220b824148c107a72609e715b6de23f0c73e8750e12ed2b5c8aa1488a18b2719310f8779e2d30",
"hex" : "48304502206d8b39ae4660df5b5ccbc93ef96bc64480447451ae2df33305b3fd0dc9492ca7022100d4bdb7dc6d6cfcddcc33ef44df0112a93fef977efacecab9268ffbcd506655e30141042f2758146f378adaf46d36680053d6ded477c6f0945820bb914220b824148c107a72609e715b6de23f0c73e8750e12ed2b5c8aa1488a18b2719310f8779e2d30"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.01005148,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c31c94ecd10f61d5b9edd92a1078cc0f20124099 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c31c94ecd10f61d5b9edd92a1078cc0f2012409988ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"AZZXeoJzQ13F5REXHuD6sTgczoUc7qXS4F"
]
}
},
{
"value" : 106.92742694,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 4c4479e2de1e73aa0db99756c6fd6afe1520c99d OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a9144c4479e2de1e73aa0db99756c6fd6afe1520c99d88ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"ANj92t5i1G5dE3otujPsqwbNBuS2t4dNia"
]
}
}
]
}

ntrn500

full member

Activity: 196

Merit: 100

As I interpret Gnosis thoughts on the delay, he is trying to tell us: "Don't worry, I am sorry" Grin

Yep everything is fine and we'll wait for another year or two, probably a decade, no one is in a hurry Grin

pebody

newbie

Activity: 10

Merit: 0

withdraw from cryptsy 2014-10-20 11:08:06 106.95742694 ANC
TrxID: 897695f63ef4752ca3848d978759dfec749ba770edb7274f6adb60328f212437
to address ANj92t5i1G5dE3otujPsqwbNBuS2t4dNia

and still nothing... Sad

CookieL

newbie

Activity: 22

Merit: 0

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Great update! Keep up the good work.

AlexGR

legendary

Activity: 1708

Merit: 1049

Quote from: Gnosis- on October 22, 2014, 04:49:19 AM

Quote from: robinson5 on October 22, 2014, 01:56:02 AM

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Do you have any reason why only 2 days before a release date you had to extend it 2-3 months? It's hard to understand why that announcement couldn't have happened earlier rather than misleading investors.

First, let me say that software estimation is a notoriously hard problem. I'm not saying I couldn't have done better -- I could have.

Basically up until a few weeks ago, I was working mostly with libzerocoin, which is code I understood really well. I was giving completion estimates based on my (relatively fast) progress with that. Then, I had to switch to working with the wallet's code itself, and that is far more complicated. By the time I became aware of how much more time it would take, it was only a few days before the testnet release deadline. There may have been some wishful thinking going on too, which I didn't catch because all my thoughts were taken up with how to solve the problems at hand.

2-3 days to 2-3 months is a very "problematic" miscalculation, no matter how you see it.

Investment wise? "This is ridiculous" -> DUMP
Confidence wise? "If the dev can't tell if it takes 2-3 days or 2-3 months, then he is either a liar/scammer/pumper or totally incompetent"

I have ANCs from back in the day when ANC and DRK were the only players around in the anon industry (DRK as main, ANC as hedge) and I'm loosely following ANC for this reason throughout the months, but, seriously, the "I miscalculated" angle can't be digested Huh

rel-oad

newbie

Activity: 57

Merit: 0

Dev has scammed us all with this recent announcement, "it'll be ready any day now.. any day now... oh wait I need another 3 months".

The coin doesn't even work right now moving between exchanges.

Sometimes it's prudent to hold during a crash - not this time.

A developer like this will not make a successful coin. You will not become a millionnaire buying into this developer.
Dump this coin into the ground and move on, there's plenty of better alternatives.

Gnosis-

member

Activity: 101

Merit: 10

Quote from: robinson5 on October 22, 2014, 01:56:02 AM

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Do you have any reason why only 2 days before a release date you had to extend it 2-3 months? It's hard to understand why that announcement couldn't have happened earlier rather than misleading investors.

First, let me say that software estimation is a notoriously hard problem. I'm not saying I couldn't have done better -- I could have.

Basically up until a few weeks ago, I was working mostly with libzerocoin, which is code I understood really well. I was giving completion estimates based on my (relatively fast) progress with that. Then, I had to switch to working with the wallet's code itself, and that is far more complicated. By the time I became aware of how much more time it would take, it was only a few days before the testnet release deadline. There may have been some wishful thinking going on too, which I didn't catch because all my thoughts were taken up with how to solve the problems at hand.

drAGon925

hero member

Activity: 527

Merit: 500

We can see drk/sdc trolls , with well known methods , some is like supporting ANC..

I tested BTC38 from my wallet to exchange, and back.. everything is ok for me.
I will not try to test cryptsy for now : )

BTC38 supporting ANC for long time as only anon coin, and I see they don't have drk..
By that, I can think that others are corrupt by drk fans/devs to make problems with ANC..
Just a thought..

drk had took good stake from their pump, they have much power/btc.
This is war my friends, there is much money in game.

dotatbg

newbie

Activity: 6

Merit: 0

Quote from: mullick on October 21, 2014, 03:31:21 PM

Quote from: K1773R on October 21, 2014, 12:07:37 PM

Craptsy is now refusing to do anything to get their stuck TX's resolved:

Code:

 K1773R: craptsy responded upon the request to give raw transaction to me (they had closed ticket) by their usual rambling about fixing this issue with anoncoin devs
 damn its worse than before they dont even broadcast nor are willing to give raw transaction now
 yoyo: you see! they refuse to do anything

They refuse to give me/us the transactions and refuse (no idea if its with intent) to broadcast the TX.
Therefore, all TX created by craptsy for ANC cannot be mined unless they change this again.

We had enough problems with Craptsy, this shows just another case of them refusing to follow the protocol or care about its customers. Please stay away for your own sake.

I received the first request for a raw transaction today. To say I have done nothing to remedy the situation is a blatant lie as I was cooperating in pm with you and the other developers.

In no way are we refusing to "Follow the protocol" We run an unmodified anoncoind and send all transactions via "sendtoaddress". Out of the 236 currencies we list. ANC is the only one with this issue

You can say its a cryptsy issue all you want. But anyone that reads the facts can see that is not the case

So you can prove it very easy. Just post a non broadcast or stuck raw transaction

Because in my test node no pending withdraw transaction with ID from my Cryptsy account

dotatbg

newbie

Activity: 6

Merit: 0

Quote from: K1773R on October 21, 2014, 11:04:15 AM

Quote from: dotatbg on October 21, 2014, 03:00:06 AM

Quote from: entertheabyss on October 20, 2014, 09:26:40 PM

2) Non standard transactions being propagated by Cryptsy. These transaction are more 100kb in size. By default anoncoin clients do not send out transaction of these size and standard miners do not accept them. Cryptsy has refused to acknowledge that they are doing anything wrong.

And then what? Coins will stay in then middle of nowhere forever?
Cryptsy said

Quote

The transaction does not need to be resent as it is a valid transaction.

but you told non standard transaction. I thing you should patch anoncoin client asap because when this "non standard transaction" has valid txID and in that case it's a valid and should be send and confirmed.

nope, see my post above.
its not about having a "valid" txID nor anything like this. the problems lies in creating too big transactions. seems they managed to even lower the fee more which resulted in failure of tx broadcast (there is a limit).

How can you be sure about too long transactions? They still refuse all requests to post a raw transaction from his mempool. The only thing we know is "Cryptsy do not broadcast some kind of transactions" The right way IMHO:
- Cryptsy post a stuck raw transaction and all we will see what is going on.
- Update your client to broadcast any transaction without limit, or reasonable one.

If his API really use sendtoaddress the problem with too big transactions is your I mean in anc node soft

Zarmung

member

Activity: 90

Merit: 10

Quote from: K1773R on October 21, 2014, 12:05:00 PM

Quote from: Zarmung on October 21, 2014, 11:34:33 AM

lol who said ZC will be emplement into Anoncoin - nonsense and scam...
The developers of ZC clearly wrote that their goal was Bitcoin but Bitcoin foundation rejected ZC's team offer.

btw ZC team is a group of scientist who work for the grants to find out something new and testing ZK protocol.
there is no connection between ZeroCash and AnonCoin except SCAM.

You, Sir, are a complete moron! We refer ZC to ZeroCoin, not ZeroCash.
Read the wiki, understand it or go elsewhere.

Stop fooling people!
First: Zerocoin is the coin which would converted from Bitcoin network through Zerocash protocol to coin called Zerocoin. There is nothing to do with Anoncoin.

Powerful group of scientists with huge funding are still working on ZC protocol becoz it has a lot of bugs and you want to say that two lame coders almost for free could do the same task? bugaga... yep.... maybe i'm not smart enough but this thing that Anon SCAM of the year i understood clearly

Second: you are huge bagholder who ignored a few rules:
- before invest money, try to understand the fact
- before say to someone moron try to say something intelligible

btw: i know some very very black rumors about Anoncoin but keep it a secret

shtako

hero member

Activity: 779

Merit: 502

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Keep up the good work! Don't care about the trolls or the people who are butt hurt after loosing some btc at the last pump/dump.

One thing people seem to have forgotten. The price is exactly the same as it was 2 months ago. That mean that in the last 2 months there have been absolutely no loss for anoncoin holders. But due to the volatility and the recent pump and dump some people have gained a lot and others have lost a lot.

robinson5

full member

Activity: 130

Merit: 100

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Do you have any reason why only 2 days before a release date you had to extend it 2-3 months? It's hard to understand why that announcement couldn't have happened earlier rather than misleading investors.

stealth923

legendary

Activity: 1036

Merit: 1000

Quote from: Gnosis- on October 22, 2014, 12:28:50 AM

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

So your dumping / accumulation phase has finished again..Rinse/Repeat eh..

Please dont set anymore dates....Come back when its working, dont ask for anymore donations.

Fool me once shame on you, Fool me twice, shame on Me.

Gnosis-

member

Activity: 101

Merit: 10

I haven't replied here in a while because the signal-to-noise ratio is really low in here (where "noise" includes things like trash talking me and speculation on the price). If you said something addressed at me here, I probably didn't read it. PM me if it's important.

Yes, estimating the time to complete software is not my strong suit, but that is a difficult problem in any case. The fact remains that I have worked hard on this and will continue to do so. I am not aware of any other developers who have made nearly as much progress (judging by public commits) in adding zero-knowledge cryptography to cryptocurrency. As for ShadowCoin, I looked at their code briefly and did not see a single commit related to this; sure, they might be keeping all the development secret, but "talk is cheap". If you look at Github, you'll see that I did more than talk. Tongue

Anyway, I am now thinking it is better to have a series of testnets with gradually increasing Zerocoin functionality, rather than a single one with all the functionality as I originally planned. I'll set a date for the first one when I am actually code complete. You can think of these as "milestones" for completion.

As for the wild oscillations in difficulty, I am working with two other people on our IRC to get this resolved.

Topic: Official Anoncoin chat thread (including history) - page 75. (Read 530606 times)