Search content
Sort by
Showing 6 of 6 results by dotatbg
Seems legit
Sure! DevTeam already do a heavy coding work. Stay tuned!
Code:
anoncoind gettransaction 013a84aeedfefff1c2ea0705ca52b0cedbb588ef2477aca3c7d392ee91cae0cc
....
....
Successfully broadcasted from my test node - and already confirmed
p.s. Maybe someone should donate me.
Craptsy is now refusing to do anything to get their stuck TX's resolved:
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.
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
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
No. My stuck transaction is 9d116e6876d045b622e3dfa0db354a9761a2750f0122d6e601be1ac4fb5d61da. Can you give me a raw transaction?
Craptsy is now refusing to do anything to get their stuck TX's resolved:
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.
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
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 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. 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
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.