|
My vote for XWC.
Keep up the good work !!!
|
|
|
|
|
Despite some unpleasant things that makes Cryptsy, I consider sharing safest of all altcoins and I think it has never been hacked.
Safety is the most important thing in this.
|
|
|
|
|
My congratulations for the great job the entire team WCF !!
|
|
|
|
What is actual total number of CENTS? All the info I find says 1 billion total.... but there are far more than a billion, I alone have well over a billion. If anybody has any insight into this, that would great, I would message shakezula, but he hasn't been active in months. Thanks!
 I cant quite figure out what this means... does it answer my question? I honestly don't know. moneysupply 49,373,328,205,100 is the maximum amount of current coins. However, to say that that amount is likely much lower in reality, because in the first few months of this coin, many coins were lost by a bifurcation. For months the problem is solved and the currency works PERFECT. |
|
|
|
|
Whitecoiners Hello, first of all congratulations for the increase in price and trading volume to all who have believed in this project, I'm on board this train because I am convinced that this has only just started.
I also want to congratulate all the members of the WCF, for the great work done at malbee on his recent appointment (it's a guaranteed success) Oizopower and especially for his great work with WhiteOS.
On the subject of voting proposed Nexby, say that I quite agree with, we should mark some limits to prevent abuses of power, but I understand that you must have more weight in the voting someone who invests $ 5,000 (risking your money ) to another invest only $ 5.
Best Regards
|
|
|
|
|
It's nice to see the slow and steady growth of WC.
Each day that passes I am more convinced that WC will be great.
Keep up the good work!
|
|
|
|
|
CENT no longer listed on exchanges with more volume, unless a drastic reduction in the number of coins is made
|
|
|
|
|
Hi jack, I finally get my coins, I did recover and the passphrase "I do not want to put a password on the recovered wallet and I know what can be the Consequences.".
That will return a wallet with several formats that SI PrivateKey me accept the client-QT.
Post some BTC, along with my thanks and admiration for his work.
Txid: 7aeb5d18f9c81d7b0bd659dd4dfd976d2f8c5af5ba2b9fb1060db8d64ef8db13
|
|
|
|
 "addr": "WX4ym8VT5UdBVjwLHoU8RZH7czCq3MGDgP", "compressed": true, "encrypted_privkey": "364b78121c64b0b5a259ef598d65d507fdbd68e431d10e7709a7b353cadeb34e", "pubkey": "02009671ba6842ecb26f6c01596deb1bce974f47390cd84c606d00fdef8c54072a", "reserve": 1 }, { "addr": "WeTWSh8sm5P7udNQvjUaLBg8j9RkNyxb8p", "compressed": true, "encrypted_privkey": "79c0da3eea56c10d884307b73f3bb161e6db334ff9d7cd91ce94d56ad9eb5d55", "pubkey": "02009edaa5203f33b079f2d813850bf2f84bfcde2a60034c41e039a48d88481770", "reserve": 1 }, { "addr": "WQhQibwwxDBsCXeVzzJYjd1kgffd8fqxv4", "compressed": true, "encrypted_privkey": "c5008c3c2c9ff673620396fe411b480327d59b782b4fd0bfe35a2155274bbbd9", "pubkey": "0200c2c3c087e3b83b767aeefa47be7244128c96a8b893b4b61e383355a1774cc1", "reserve": 1 }, { "addr": "Wk2RUci9hayr2oNpRBKo3hqPVCeMRprj2U", "compressed": true, "encrypted_privkey": "30be2c08f15332ed3ded01ebd263cc363a42471b3c496d36723ff2dd79da56c9", "pubkey": "0200c6c02eabd66a884a7167a9e9e22d78cdb2c59a9729dcdcf70daeec850f01f6", "reserve": 1 }, { "addr": "WYgi8xY7fWC8q5dUYAaD5WEmcK6quPTNs7", "compressed": true, "encrypted_privkey": "7258740357872c98c1060a0031348a536fac0b5441cd6741a76fd3b90214254f", "pubkey": "0200f00b0494608a365cb3436903fe6bce15810903ae401832be6dbbbadff98b12", "reserve": 1 }, Jack, I send you what you ask and capture several privatekeys (no value), if you are helpful. Thank you |
|
|
|
|
GUI gives me this other error:
Constant Numerica Incorrect: 4e4.
Line: 1 Character: 38
parser error: <4e4: String> [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId: BadNumericConstant
|
|
|
|
The tool I sent you transforms hexadecimal privkey to base58. Then you can import with the command line in the GUI client.
By the way, did you try using the recovered wallet (from pywallet --recover) directly as wallet.dat?
This last wallet I have not tested on the client-qt (now I try). error: generated but not accepted You can not start keypol GUI gives me this other error: parser error: <4e4: String> [], ParentContainsErrorRecordException + FullyQualifiedErrorId: BadNumericConstant |
|
|
|
The tool I sent you transforms hexadecimal privkey to base58. Then you can import with the command line in the GUI client.
By the way, did you try using the recovered wallet (from pywallet --recover) directly as wallet.dat?
This last wallet I have not tested on the client-qt (now I try). |
|
|
|
Oh it's for an altcoin! The problem must be this.
Please create a dummy address in your client then export the coresponding private key through the console and post it here.
I highly advise you to delete the address afterwards.
Thanks to this I'll be able to know which leading byte your altcoin uses to export private keys.
PS: without quotation marks
As you indicated me I made a dumpprivkey created and removed for the occasion wallet and this is what it returns me: WnPrHA434nWat8CL131TTsZ3w2GYXm15ConQfcMjpNg2zwiG2kJB I have taken other privatekeys and let you know that all start with W It does not look anything like the PrivateKey to recover remanded me, 52 characters instead of 64 characters. Let me know if you can do something about it. greetings Great! I changed pywallet a bit to make a script for you I just added those lines (do a diff before running it if you want): if len(sys.argv[1])==64:
print EncodeBase58Check(chr(201)+(sys.argv[1]).decode('hex')+'\x01')
else:
print 'bad private key length (%d)'%len(sys.argv[1])
exit() The result is here: http://pastebin.com/raw.php?i=VYJkFfMcJust save it to privkey.py then python privkey.py 2a5b4c4e1d5f...(64 hexadecimal characters) Hi Jack, I will make the process has returned to recover and bounce back and the new dump.txt the address where I sent coins or any other address Whitecoin not appear. The addresses are all BTC me back (all start with "1") when the last time found many WC, plus all PrivateKeys are 64 characters (hexadecimal) instead of 52 (base58). Of course I keep the previous dump.txt with the correct address and associated PrivateKey. Is there any way (calculator, converter ...) that can convert the PrivateKey that I have associated hexadecimal to base58? Thanks again |
|
|
|
Oh it's for an altcoin! The problem must be this.
Please create a dummy address in your client then export the coresponding private key through the console and post it here.
I highly advise you to delete the address afterwards.
Thanks to this I'll be able to know which leading byte your altcoin uses to export private keys.
PS: without quotation marks
As you indicated me I made a dumpprivkey created and removed for the occasion wallet and this is what it returns me: WnPrHA434nWat8CL131TTsZ3w2GYXm15ConQfcMjpNg2zwiG2kJB I have taken other privatekeys and let you know that all start with W It does not look anything like the PrivateKey to recover remanded me, 52 characters instead of 64 characters. Let me know if you can do something about it. greetings |
|
|
|
I'm glad it worked Actually I should make a message about that Tell me how it goes  Hi jack, recover after running the 2728 I got that overturned privatekeys a txt file. privatekeys one of those 2728 matches the address to which I sent the coins, but can not get the client-QT import. It gives me an error message: "invalid private key (code -5), to make sure it is not that the private key is incorrect I have tried many of the other import privatekeys 2728 with the same error. I write the syntax in the client console-QT is importprivkey xxxxxxxxxxxxxxxxxxxxxxxx For that matter please tell me if the PrivateKey have to enter with or without quotation marks (of course I've tried every possible way, but it'll be safe and next time). I have also tried to import them pywallet: pywallet \ pywallet.py --datadir c: \ users \ jesus \ appdata \ roaming \ whitecoin --namecoin importprivkey xxxxxxxxxxxxxxxxxxxxxxxxxxxx It gives me the following error: 'ecdsa' package is not installed I have reinstalled python, pycrypto, bsddb, zope, twisted and finally setuptools4.1 Not know what I'm doing wrong, I really appreciate your help. greetings |
|
|
|
hello, I have a problem with a wallet deleted by mistake. I recovered with recuva but after copying it to a flash drive formatted and after applying the pywallet says " 0 wallets recovered , 0 recovered private keys" so I assume that this wallet is totally corrupt. Now I installed windows7 on a new hard disk (installed python27, pywallet, setuptools 4.1b1, bsbbd 3-6.0.1, pycrypto2.6, Twisted 14.0.0, python ecdsa) and the old record is not system disk. Now I'm trying this: https://bitcointalk.org/index.php?topic=34028.msg2794856#msg2794856 to try to recover private keys and wallets pywallet running from the new C: using this syntax: pywallet \ pywallet.py --recover --recov_device f: --recov_size 180Gio --otherversion=73 --recov_outputdir c: \ recover f: is the drive letter of the old drive but it gives me the following error: error: <13, "permission denied" Help would be greatly appreciated Before anything else: run cmd with admin, not with a regular user Windows menu -> search "cmd" -> right-click on cmd -> run as admin. Then enter the command. The prompt will be "C:\Windows\system32" instead of "C:\Users\xxx" I'm not sure this is the problem but it is necessary anyway Thank you! I've been stupid! is now working If I have success I'll send some your directions BTC forum I have been a big help |
|
|
|
hello, I have a problem with a wallet deleted by mistake. I recovered with recuva but after copying it to a flash drive formatted and after applying the pywallet says " 0 wallets recovered , 0 recovered private keys" so I assume that this wallet is totally corrupt. Now I installed windows7 on a new hard disk (installed python27, pywallet, setuptools 4.1b1, bsbbd 3-6.0.1, pycrypto2.6, Twisted 14.0.0, python ecdsa) and the old record is not system disk. Now I'm trying this: https://bitcointalk.org/index.php?topic=34028.msg2794856#msg2794856 to try to recover private keys and wallets pywallet running from the new C: using this syntax: pywallet \ pywallet.py --recover --recov_device f: --recov_size 180Gio --otherversion=73 --recov_outputdir c: \ recover f: is the drive letter of the old drive but it gives me the following error: error: <13, "permission denied" Help would be greatly appreciated |
|
|
|
Our big problem is a lack of trust among investors and traders (that is, anyone fears to be dumped by others). We have to solve it. I propose to build up a mailing list of investors. To subscribe, one have to declare an address (or multiple ones) with a minimum number of coins in total (ie 1m). The system can validate the address(es) by asking to move a random number of coin between 0 and 1 to a donation address in a specific time frame. The subscription is valid until the coins remain untouched in the declared address(es). Each member can freely talk with others in order to build up confidence. Declared addresses, number of members and so on can be publicly available (something like http://www.richlist.eu/whitecoin). Without a minimum of confidence among "big" investors we don't go anywhere. What do you think? I'm in for this !! |
|
|
|
|
I think there has been a conspiracy between cinnicoin, rynomster and battbot in Cinni.
The prestige of cinnicoin not worth anything and if it does not end with handing over the keys to the community Cinni, battbot and has rynomster will end up just like cinnicoin.
|
|
|
|
|
Show Posts
