Search content
Sort by
Showing 20 of 101 results by Gnosis-
How about some level of moderation for this thread?
Are you not concerned about these things?
1. K1773R is still blaming the transaction problem on cryptsy. There have been bugs found in the anoncoin code and cryptsy is compiling from source. Other exchanges and even desktop qt clients are having the same problem as cryptsy. So this can't be a cryptsy problem. I would really like if the devs would work on this problem seeing as a cryptocurrency with transaction problems is obviously really bad. What are the devs doing to fix this? We need anoncoin back on exchanges asap.
K1773R is in agreement that we should switch to the 0.9.3 codebase.
Quote
2. Meeh has been working on myriad auxPoW for the past month but recently asked what myriad auxPoW is. Since he can't develop something he doesn't know about what has he been doing? An update on the supposed "imminent" hardfork would be great. The sooner this hardfork happens the sooner anoncoin can fix the difficulty issue.
3. Anoncoin code is still based on bitcoin 0.8.6 which is almost a year old at this point. Why hasn't the anoncoin code been updated? Bitcoin is currently on 0.9.3 and there have 4 updates in between 0.8.6 and 0.9.3. Why has anoncoin missed all 4 updates? Gnosis recently posted that meeh was working on updating the code to 0.9.3 but that concerns me because meeh was also supposed to be working on myriad auxPoW but seems to not be doing too well with that either.
3. Anoncoin code is still based on bitcoin 0.8.6 which is almost a year old at this point. Why hasn't the anoncoin code been updated? Bitcoin is currently on 0.9.3 and there have 4 updates in between 0.8.6 and 0.9.3. Why has anoncoin missed all 4 updates? Gnosis recently posted that meeh was working on updating the code to 0.9.3 but that concerns me because meeh was also supposed to be working on myriad auxPoW but seems to not be doing too well with that either.
Meeh definitely knows what myriad is, so this was probably a misunderstanding. Anyway, I am doing the porting to 0.9.3 and adding a replacement for KGW. Our faulty difficulty algorithm is a major contributor to block difficulty oscillation. After all this is released, either myself or another developer (probably not meeh) will work on myriad auxpow. Meeh seems to be extremely busy with his job these past weeks, but we are capable of doing this without him.
Quote
4. This conversation with ian miers of zerocash is also troubling. He doesn't seem to think our RSA UFO's are strong enough. https://twitter.com/secparam/status/449576116161089537
He doesn't seem to get it. Maybe Twitter is the wrong medium for such conversations.
It appears that he thinks an n-bit random integer has a 100% probability of being factored in T time by an attacker (in other words, he thinks there's no variation in time to factor). This is definitely not the case. Also, if it was the case, then the Sander UFO construction would not be secure.
entertheabyss is another troll created to discredit Anoncoin
People need to understand the hierarchy and scope of the trolls infesting anc.
1) Through collusion, subversion or other means they own at least two anc devs apparently.
2) There are at least four full time people working on developing this scam.
3) A lot of money has been invested in suppressing the price. This was first done with throwaway miners. Most miners immediately sell an average of ~90% of the coins the mine. By cornering mining activities the anc manipulatiors are able to keep the price low yet still maintain longterm control when the price rises.
4) Almost certainly their plan involves several phases, each of which will feature an artificial price run up followed by a crash and increasing loss of confidence in the anc brand.
5) It still is not clear whether the group is a government entity trying to push people toward government created algorithms which have backdoors, like cryptonote, or if it is a private group of profiteers.
Question: You are implementing Zerocoin. But from what? Zerocoin project was never finished, code does not exist? Or are you guys writing the code yourself, based of the Zerocoin white paper? Can you clarify? I made some ANC investments, but I need to have this clarified to be able to invest more.
The Zerocoin project was partially finished in the sense that researchers at JHU wrote a library called libzerocoin last year. I have used libzerocoin as a starting point though of course the white paper was essential for understanding it.
So far I have fixed bugs in libzerocoin (including a couple of very critical ones), and adapted it to support RSA UFOs (read the wiki page to see why it is necessary). This is all complete. The remaining work is to integrate libzerocoin into the Anoncoin wallet software, and this is currently in progress. All public commits are in https://github.com/Anoncoin/anoncoin/tree/zc though I am continuing development privately to avoid copy-cat coins.
One more thing about 0.8.5 bug. In wallet.cpp after line 745 (AddSupportingTransactions part) you should add 3 more lines:
else
{
continue;
because if there was no else continue statement it can stores empty transaction,but else continue will prevent invalid vtxPrev coming in the wallet and already existing empty transactions from transmitting.
Consequently it will protect nodes from being banned
else
{
continue;
because if there was no else continue statement it can stores empty transaction,but else continue will prevent invalid vtxPrev coming in the wallet and already existing empty transactions from transmitting.
Consequently it will protect nodes from being banned
Thank you so much thunderjet and GroundRod for looking over the code! Hopefully the two errors in the code you pointed out will solve the transaction issues and cryptsy will allow anc deposits and withdrawals again. But why is our code based off of 0.8.5 instead of the more updated 0.9.3?
Meeh is working on switching to 0.9.3
In the meantime, I fixed this in the master branch by finding the commits to Bitcoin that fixed this and cherry-picking them:
https://github.com/Anoncoin/anoncoin/commit/c93e385af816503f6cd2ff61353d12a9121a86b5
https://github.com/Anoncoin/anoncoin/commit/de779467e43b4503f89d9b9ea063f745403b2528
thunderjet, is this what you had in mind?
Thanks Gnosis for quick answer on mine previous question.Now I found something much more serious.In Bitcoin before v0.8.6 wallet.cpp code had one serious bug which allows relaying of invalid transactions.Error in code allowed insertion of empty transactions into vtxPrev which nasty consequence was that nodes whose transmitting such transactions were banned - causing shutdown parts of network, problems in nodes communications and acception of transactions.This bug was never fixed in Anoncoin wallet.cpp:
Bug is on wallet.cpp Line 850 of anoncoin code - if (!tx.IsCoinBase()) should be if (!tx.IsCoinBase() && !tx.vin.empty())
Bug is on wallet.cpp Line 850 of anoncoin code - if (!tx.IsCoinBase()) should be if (!tx.IsCoinBase() && !tx.vin.empty())
@thunderjet - Excellent find! Spent allot of time in that RelayWalletTransaction(), convinced that was where the problem must be @. My initial reaction here is that you've nailed it. My experience is primarily with the 0.9.2+ codebase & there is significant differences between the two there, did not know that about 0.8.6. We'll have to see what Gnosis thinks, but I'm really happy you pointed this out!
This is encouraging! I'll take a closer look when I wake up in ~9 hours.
Anoncoin rpcwallet.cpp is broken.That is a probable cause of wallet erratic behaviour.Error in code for wallet tx - JSON connection :
Line 41 - if (confirms) should be if (confirms > 0)
Line 41 - if (confirms) should be if (confirms > 0)
No, sorry, that's not a bug. Perhaps it's not good coding style, but it's not a bug.
It could only be a bug if confirms could ever be less than 0, which is impossible, as you can see from CMerkleTx::GetDepthInMainChain (main.cpp lines 898-921).
Keep looking.
EDIT: You may have noticed this by comparing with the Bitcoin code, where it says (confirms > 0). This was changed in February at the same time that CMerkleTx::GetDepthInMainChain was modified to return -1 in the case of a "conflicting transaction." Anoncoin's code does not need this check because our version of said function never returns a negative value.
[...]
Zerocoin will not work. Either by design or by accident it is fatally flawed. The only way it would work is to design something completely different and call it zerocoin.
[...]
Zerocoin will not work. Either by design or by accident it is fatally flawed. The only way it would work is to design something completely different and call it zerocoin.
[...]
Why do trolls have to be so long on rhetoric and short on facts and evidence? You're just flat out claiming it won't work without any attempt to support that claim.
I can already see where this is going to go... you're going to reply with "evidence" and when people refute it, you'll just ignore it and move on to a different angle of attack.
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.
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.
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.
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.
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.
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.
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.
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.
Should all the code be open source in Github if we are still 2-3 months away?
Is there anyone (hero member with a perfect reputation) that could maybe hold new donations in escrow as a reward for new developers to help Gnosis finish the project on a contingency basis (only getting paid upon completion)?
Gnosis, if someone were to help you, what would you need the most? Math experts? More programmers? Both? Can the remaining work easily be subdivided so multiple people can work on it at once?
Is there anyone (hero member with a perfect reputation) that could maybe hold new donations in escrow as a reward for new developers to help Gnosis finish the project on a contingency basis (only getting paid upon completion)?
Gnosis, if someone were to help you, what would you need the most? Math experts? More programmers? Both? Can the remaining work easily be subdivided so multiple people can work on it at once?
I would say the math part has been easiest for me. It would really only take one other good C++ coder (especially one who's familiar with the Bitcoin/Anoncoin codebase) to speed this up a lot.
This is fucked up. From an assured Oct 15th testnet, to a week delay, to a 2-3 month delay. There's really nothing I can say, very weird way of acting.
When the darkcoin dev made a few mistakes along the way, I always felt assured that he would pull through with results, since he had his real name and face out there since day 1 (and had been delivering actual results) . With gnosis it feels like he can just walk away from all this stuff if he decides to and no one can hold him accountable for it. If he feels the task is too big after all, all he needs to do is stop posting.
When the darkcoin dev made a few mistakes along the way, I always felt assured that he would pull through with results, since he had his real name and face out there since day 1 (and had been delivering actual results) . With gnosis it feels like he can just walk away from all this stuff if he decides to and no one can hold him accountable for it. If he feels the task is too big after all, all he needs to do is stop posting.
These "delays" are going on for around a year already.
Do not send any donations. As long as they receive donations they will pretend an activity "2 weeks" (TM). If gnosis was ever serious he would finish the coin long time ago and could become rich instantly from its repricing. But he is focused on cashing the donations only. Why is that?
If I was not serious about implementing Zerocoin, don't you think I would have cashed out my donations by now? Note that they haven't moved: http://ancblockchain.com/address/AU4hFCFZLhB2gTyG4VbaEurXGrTMNW2nu6
If I may, I'd like to make some suggestions to the ANC team...
Before the move to zANC I think it would be wise to fix the KGW issue; I don't think K1773R wants to spend his life mining 100k tx when the volume of transactions goes up. It doesn't need to come with the myriad if this is holding ANC back; these could be sequenced.
@ meeh it'd be nice to get an idea of when the fix will be made.
@ Gnosis it seems like a heavy schedule during the 1 week assumed to deliver the zANC testnet... Personally I don't like to get news of delays 1 day before a deadline - it's much better to assume things take 2X or even 3X longer when setting a deadline and deliver ahead of schedule (if things are ready); this fuels much more positive cycles. I know that this is complex and difficult to plan, it's only a matter of managing expectations from the community.
Before the move to zANC I think it would be wise to fix the KGW issue; I don't think K1773R wants to spend his life mining 100k tx when the volume of transactions goes up. It doesn't need to come with the myriad if this is holding ANC back; these could be sequenced.
@ meeh it'd be nice to get an idea of when the fix will be made.
@ Gnosis it seems like a heavy schedule during the 1 week assumed to deliver the zANC testnet... Personally I don't like to get news of delays 1 day before a deadline - it's much better to assume things take 2X or even 3X longer when setting a deadline and deliver ahead of schedule (if things are ready); this fuels much more positive cycles. I know that this is complex and difficult to plan, it's only a matter of managing expectations from the community.
Agreed with the above!
Would also like to add that the proposed schedule outlined by Gnosis looks very heavy and I would infer unrealistic.
I rest my case
Yes, it was very heavy. In any case, I am still committed to getting this done, just not in the original time frame.
It's probably too much to ask, but for all of you panicking about the price dropping, hold tight because this is only temporary. I remember when BTC dropped from $30 to $2 and stayed there for months, before going back up to $60 and beyond. A coin dropping in price does not mean it's dead.
I underestimated the scope of this project and set too ambitious of a schedule for it. Zerocoin will be probably be ready within 2-3 months, but I don't want to give any more release dates (either for testnet or mainnet) until I am very, very close. I will not make this mistake again.
I will continue to give status updates, and I have made tremendous progress in recent weeks. As I promised, I will still work full time on this until November 1, and I expect to have a few hours a day after that to work on it.
I will continue to give status updates, and I have made tremendous progress in recent weeks. As I promised, I will still work full time on this until November 1, and I expect to have a few hours a day after that to work on it.
It's too late in the day for me to make a progress update, except to say that I have been writing code at a very rapid pace You all can expect a real update in ~21 hours.
Generally the quieter I am on btctalk and IRC, the more work I am getting done, so don't worry if I'm not posting much here!
You all can expect a real update in ~21 hours.Generally the quieter I am on btctalk and IRC, the more work I am getting done, so don't worry if I'm not posting much here!
Done:
CWalletCoin
zerocoin_wallet storage
RPC mint txn (but still need a high level command: "mintzerocoins")
relaying mint txns
Almost done:
accum. chkpts in block
Next:
wallet witness update
wallet mint logic
refactor CoinSpend
RPC create spend + impl.
store own spend pieces locally
RPC get seeding spend proofs
net: seed spends
net: receive and verify spends
store received spend pieces
wallet spend logic
2 1/2 days debugging
(GUI if time permits)
I'm a little bit behind schedule, but I have more time each day for the next 4 days, so I'll definitely be able to catch up.
CWalletCoin
zerocoin_wallet storage
RPC mint txn (but still need a high level command: "mintzerocoins")
relaying mint txns
Almost done:
accum. chkpts in block
Next:
wallet witness update
wallet mint logic
refactor CoinSpend
RPC create spend + impl.
store own spend pieces locally
RPC get seeding spend proofs
net: seed spends
net: receive and verify spends
store received spend pieces
wallet spend logic
2 1/2 days debugging
(GUI if time permits)
I'm a little bit behind schedule, but I have more time each day for the next 4 days, so I'll definitely be able to catch up.
Here is an update before I sleep: I've been fixing some issues and general improvements to lay the groundwork for tomorrow. I'll catch up to schedule then.
Also, thanks Alacast for helping people help themselves.
Also, thanks Alacast for helping people help themselves.
@ gnosis
perhaps is logically, no one asked, and you have not published,
but I have to ask, mainnet 01 November is delayed for 7 days like testnet?
perhaps is logically, no one asked, and you have not published,
but I have to ask, mainnet 01 November is delayed for 7 days like testnet?
That is likely. Mainnet launch will be somewhere between the 1st and the 7th. I'll know more a few days after testnet launch.
I'm about to go to bed, and I just wanted to report that I'm done with all tasks I promised for today.
Also, here's a glimpse of Zerocoin mint transaction creation with RPC:
Also, here's a glimpse of Zerocoin mint transaction creation with RPC:
Code:
$ r1 createrawtransaction '[{"txid":"f95e158e09edf59865e7b2357a9dcb931375cdfd08784e7e87bab1c30b72d2d2","vout":0}]' {\"ML2wW4aKfd5Qh4cmCZufzs7sVnX8d3CSKN\":3.2} {\"f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a\":0.5}
0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef90000000000ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
$ r1 signrawtransaction 0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef90000000000ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
{
"hex" : "0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef9000000004a49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000",
"complete" : true
}
$ r1 decoderawtransaction 0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef9000000004a49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
{
"txid" : "e3818acec0a45af2b1bb941254c6a9a2435909a04b1638875b96a42ee424a1bd",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "f95e158e09edf59865e7b2357a9dcb931375cdfd08784e7e87bab1c30b72d2d2",
"vout" : 0,
"scriptSig" : {
"asm" : "304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01",
"hex" : "49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 3.20000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 851a35d1bba176f4f6076878266fd5e34c5fdd80 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"ML2wW4aKfd5Qh4cmCZufzs7sVnX8d3CSKN"
]
}
},
{
"value" : 0.50000000,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_RETURN OP_ZCMINT 1 f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a",
"hex" : "6ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a",
"type" : "zcmint"
}
}
]
}
0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef90000000000ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
$ r1 signrawtransaction 0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef90000000000ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
{
"hex" : "0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef9000000004a49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000",
"complete" : true
}
$ r1 decoderawtransaction 0100000001d2d2720bc3b1ba877e4e7808fdcd751393cb9d7a35b2e76598f5ed098e155ef9000000004a49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01ffffffff0200d01213000000001976a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac80f0fa0200000000856ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a00000000
{
"txid" : "e3818acec0a45af2b1bb941254c6a9a2435909a04b1638875b96a42ee424a1bd",
"version" : 1,
"locktime" : 0,
"vin" : [
{
"txid" : "f95e158e09edf59865e7b2357a9dcb931375cdfd08784e7e87bab1c30b72d2d2",
"vout" : 0,
"scriptSig" : {
"asm" : "304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01",
"hex" : "49304602210083a8cf0654bbf62b632a3f45b3bcc0f65bfc7cbb51466607a936ce0563b83300022100b703ae5327ef5929dfcfd2a983ff67b34b0a88f5cc7a82b090e0461ec1bf239a01"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 3.20000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 851a35d1bba176f4f6076878266fd5e34c5fdd80 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914851a35d1bba176f4f6076878266fd5e34c5fdd8088ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"ML2wW4aKfd5Qh4cmCZufzs7sVnX8d3CSKN"
]
}
},
{
"value" : 0.50000000,
"n" : 1,
"scriptPubKey" : {
"asm" : "OP_RETURN OP_ZCMINT 1 f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a",
"hex" : "6ad3514c80f356163e9a9d1dc6b6bdf2c93bc54e136911b0eee588e06416989f79cb8a4bc02dcc8e15646aaa1cb1a41dd0613c488218bed062b579f29ae1dd107da3426ef732fd86735313351cce261fc70b750569321485925bd63406413793bb5be785300c5a26dafa1095a3049786a83b981f8f3f231394c8b22a3d17b0d0cd1b64666a",
"type" : "zcmint"
}
}
]
}
So this is where I get even more impatient. CAN I GET A CLARIFICATION WHEN I WILL BE ABLE TO ACCESS MY FUNDS? Is it going to take a day, two days, a week, a month?
Thanks Bittrex, for making me hold when the market is finding a bottom.
Conspiracies.
Thanks Bittrex, for making me hold when the market is finding a bottom.
Conspiracies.
We are working with Bittrex to figure out how to solve their issue. There is a good chance this solution will be relevant to other exchanges.