Latest posts of: crowning

Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 [11]

201

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][MRO] Monero - a coin with strong privacy based on CryptoNote technology

on: April 25, 2014, 08:11:40 AM

Quote from: mickey_miner on April 25, 2014, 07:50:47 AM So you have working? If so thats good. I am glad to help. Good luck mining! Yep, around 6.9 hashrate with 7 threads on my Intel i7 testbox while the system is still very usable.

202

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][MRO] Monero - a coin with strong privacy based on CryptoNote technology

on: April 25, 2014, 07:47:52 AM

Quote from: mickey_miner on April 25, 2014, 06:05:10 AM Do not start daemon/wallet on different port. Reboot computer. Start bitmonerod from command line. Let sync. "important to let finish syncing" start wallet from command line and type start_mining from within wallet. I know it more complicated than other coin for now. Devs are working on GUI to make simple and easy from Windows. It's new coin working out issues like any other. It is different from other coins. Issues will be resolved in short time. Give try and inform on status. Happy mining Edit: After bitmonerod sync, type "save" in window to write blockchain to hard drive. When closing bitmonerod type exit in window to write latest block information to hard drive. Does not write autmatically. It is important to wait until bitmonerod sync before start mining. You will see message like: You are now synchronized with the network. You may now start simplewallet. Please note, that the blockchain will be saved only after you quit the daemon wi th "exit" command or if you use "save" command. Otherwise, you will possibly need to synchronize the blockchain again. Then ready to mine. Let know if this fixes issue. Actually coming from Unix/Linux I don't mind command line applications, but at least the documentation should be correct and the script posted in the Windows tutorial does NOT work. Doing everything by hand (like in the Linux tutorial) works, so thanks for your help.

203

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][MRO] Monero - a coin with strong privacy based on CryptoNote technology

on: April 25, 2014, 05:47:56 AM

"Error: wallet failed to connect to daemon (http://localhost:18081). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address." Still get this error. The daemon is running, synced with the network, and is according to its own log listening on its default port (log: "Core rpc server initialized OK on port: 18081"). There's no local firewall, and I also started the daemon and wallet with a different port number just to make sure no one else uses this port. A telnet to localhost on port 18081 works, so someone is listening. The Windows build seems kinda buggy...

204

Alternate cryptocurrencies / Altcoin Discussion / Re: [ANN][MRO] Monero - an anonymous coin based on CryptoNote technology

on: April 24, 2014, 08:53:48 PM

Quote from: David Latapie on April 24, 2014, 08:52:13 PM Quote from: crowning on April 24, 2014, 08:51:09 PM Unfortunately there's no blockchain.bin (searched the complete drive), but maybe I have to wait here also. Hidden folder Windows? Hidden folders are visible...for now I'll just wait. If nothing happens till tomorrow I'll build the Linux wallet.

205

Alternate cryptocurrencies / Altcoin Discussion / Re: [ANN][MRO] Monero - an anonymous coin based on CryptoNote technology

on: April 24, 2014, 08:51:09 PM

Quote from: David Latapie on April 24, 2014, 08:46:07 PM ~/.bitmonero/ on Linux. Probably %APPDATA/bitmonero on Windows? Name is blockchain.bin Thanks for the sync-info. Unfortunately there's no blockchain.bin (searched the complete drive), but maybe I have to wait here also.

206

Alternate cryptocurrencies / Altcoin Discussion / Re: [ANN][MRO] Monero - an anonymous coin based on CryptoNote technology

on: April 24, 2014, 08:44:09 PM

"Error: wallet failed to connect to daemon (http://localhost:18081). Daemon either is not started or passed wrong port. Please, make sure that daemon is running or restart the wallet with correct daemon address." The daemon is running, started syncing with the network, and is according to its own log listening on its default port (log: "Core rpc server initialized OK on port: 18081"). There's no local firewall, and I also started daemon and wallet with a different port number. A telnet to localhost on port 18081 works, so someone is listening. Do I have to wait until the daemon has fully synced? Oh, and where is the blockchain persisted?

207

Alternate cryptocurrencies / Altcoin Discussion / Re: Poll: What is the best solution to the coming Scrypt ASIC problem?

on: April 24, 2014, 01:25:23 PM

Quote from: piratfx on April 24, 2014, 06:23:40 AM HEFFTY1 !, for now it's best algo ( low temp , really low fan noise, high power efficience, simple gtx 765m got 4,5MH ). I propose to check this ALGO, just mine hevay coin for a while and U will see, smooth and easy Hefty is just SHA-256, Keccak-512, Grøestl-512 and BLAKE-512 combined, in other words 4/11 of X11 (combined slightly different, though). Nice to make it collision free, but not improving ASIC resistance.

208

Alternate cryptocurrencies / Altcoin Discussion / Re: Poll: What is the best solution to the coming Scrypt ASIC problem?

on: April 24, 2014, 01:04:25 PM

Quote from: WompRat on April 24, 2014, 11:21:46 AM I would therefore recommend a switch to something else more GPU or even CPU friendly. Cuckoo Cycle seems very promising if you want the widest audience possible mining. I had just a quick look through the Cuckoo Cycle whitepaper...looks quite promising. Thanks for that pointer

209

Alternate cryptocurrencies / Altcoin Discussion / Re: Poll: What is the best solution to the coming Scrypt ASIC problem?

on: April 24, 2014, 10:59:34 AM

Quote from: DigiByte on April 23, 2014, 06:23:32 PM ...Skein looks to be the most RAM intensive. Nope, see the Skein whitepaper, chapter 5.2: http://www.skein-hash.info/sites/default/files/skein1.3.pdf

210

Alternate cryptocurrencies / Altcoin Discussion / Is this a Dogecoin fork attempt?

on: April 21, 2014, 12:02:00 PM

[Disclaimer: this is the first time I've investigated into the depths of a blockchain, so if I should have understood this completely wrong please correct me! If you need more data from my log, request it, I'm happy to help]

3 days ago I started my Dogecoin wallet (the latest 1.6.something version, downloaded from the official Dogecoin link) after being offline for 2 days and it stopped syncing at block 186741.

What I tried so far:

Re-installed the wallet, and using only the nodes listed on the official Dogecoin announcement page here in this forum
Restored blockchain from a 6 week old local backup
Completely synced blockchain from scratch into the empty Dogecoin folder

But, no matter what, sync stopped at block 186741.

Fortunately I have a debug.log for this time, this is what it says:

Code:

2014-04-20 18:45:55 received block d8768862a5cc5ddd786232982985a92122ce3159848a878a17fb966f207d5e6d
2014-04-20 18:45:55   nActualTimespan = 23  before bounds
2014-04-20 18:45:55 DIGISHIELD RETARGET
2014-04-20 18:45:55 GetNextWorkRequired RETARGET
2014-04-20 18:45:55 nTargetTimespan = 60    nActualTimespan = 56
2014-04-20 18:45:55 Before: 1b393006  0000000000393006000000000000000000000000000000000000000000000000
2014-04-20 18:45:55 After:  1b356005  0000000000356005999999999999999999999999999999999999999999999999
2014-04-20 18:45:55 SetBestChain: new best=d8768862a5cc5ddd786232982985a92122ce3159848a878a17fb966f207d5e6d  height=186741  log2_work=59.243471  tx=9278894  date=2014-04-18 16:32:14 progress=0.997577
2014-04-20 18:45:55 ProcessBlock: ACCEPTED
2014-04-20 18:45:56 received block 42baadc93c3b503e06d28ecdc225fd48eea3a237fce7926359f871bffe776662
2014-04-20 18:45:56   nActualTimespan = 79  before bounds
2014-04-20 18:45:56 DIGISHIELD RETARGET
2014-04-20 18:45:56 GetNextWorkRequired RETARGET
2014-04-20 18:45:56 nTargetTimespan = 60    nActualTimespan = 62
2014-04-20 18:45:56 Before: 1b356005  0000000000356005000000000000000000000000000000000000000000000000
2014-04-20 18:45:56 After:  1b37277c  000000000037277ca22222222222222222222222222222222222222222222222
2014-04-20 18:45:56 ERROR: ConnectBlock() : inputs missing/spent
2014-04-20 18:45:56 InvalidChainFound: invalid block=42baadc93c3b503e06d28ecdc225fd48eea3a237fce7926359f871bffe776662  height=186742  log2_work=59.243482  date=2014-04-18 16:36:39
2014-04-20 18:45:56 InvalidChainFound:  current best=d8768862a5cc5ddd786232982985a92122ce3159848a878a17fb966f207d5e6d  height=186741  log2_work=59.243471  date=2014-04-18 16:32:14
2014-04-20 18:45:56 InvalidChainFound: invalid block=42baadc93c3b503e06d28ecdc225fd48eea3a237fce7926359f871bffe776662  height=186742  log2_work=59.243482  date=2014-04-18 16:36:39
2014-04-20 18:45:56 InvalidChainFound:  current best=d8768862a5cc5ddd786232982985a92122ce3159848a878a17fb966f207d5e6d  height=186741  log2_work=59.243471  date=2014-04-18 16:32:14
2014-04-20 18:45:56 ERROR: SetBestBlock() : ConnectBlock 42baadc93c3b503e06d28ecdc225fd48eea3a237fce7926359f871bffe776662 failed
2014-04-20 18:45:56 ERROR: AcceptBlock() : AddToBlockIndex failed
2014-04-20 18:45:56 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-20 18:45:56 Misbehaving: 69.245.81.106:22556 (0 -> 100) DISCONNECTING
2014-04-20 18:45:56 disconnecting node 69.245.81.106:22556

Does this "misbehaving" node 69.245.81.106 try to manipulate things or is it normal that clients are misbehaving due lack of programming skills?

After this, I got a couple of hundreds "received block ...", "Process block: ORPHAN BLOCK, ...." message pairs.

After that, for each(!) incoming new block I get:

Code:

2014-04-20 18:47:29 received block 5ca10c212bf91a77fac7fa181574d97b2b2b238ae57aa2b37ba9aa149c1c3c62
2014-04-20 18:47:29   nActualTimespan = 265  before bounds
2014-04-20 18:47:29 DIGISHIELD RETARGET
2014-04-20 18:47:29 GetNextWorkRequired RETARGET
2014-04-20 18:47:29 nTargetTimespan = 60    nActualTimespan = 85
2014-04-20 18:47:29 Before: 1b37277c  000000000037277c000000000000000000000000000000000000000000000000
2014-04-20 18:47:29 After:  1b4e229a  00000000004e229a555555555555555555555555555555555555555555555555
2014-04-20 18:47:29 InvalidChainFound: invalid block=5ca10c212bf91a77fac7fa181574d97b2b2b238ae57aa2b37ba9aa149c1c3c62  height=186743  log2_work=59.243489  date=2014-04-18 16:37:51
2014-04-20 18:47:29 InvalidChainFound:  current best=d8768862a5cc5ddd786232982985a92122ce3159848a878a17fb966f207d5e6d  height=186741  log2_work=59.243471  date=2014-04-18 16:32:14
2014-04-20 18:47:31 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2014-04-20 18:47:29 ProcessBlock: ACCEPTED

The "Displayed transactions may not be correct..." message is also displayed within the wallet.

I've never seen this this with any coin before. Is this normal, should I be worried and most important, how can I stop/work around this to sync my wallet again?

Any help highly appreciated!

211

Bitcoin / Mining / Re: Earth hour. does anyone mining care?

on: April 16, 2014, 06:12:20 PM

I'll point my miners to an Earthcoin pool for one hour!

212

Alternate cryptocurrencies / Altcoin Discussion / Re: to coin devs: VERSION and DATE please always mention, for easier wallet updates

on: April 13, 2014, 12:15:32 PM

Bumping this one because I just had a hard time finding a Litecoin wallet from an official source which says the heartbleed bug is fixed [1] Litecoin.org: no info Litecoin.info/Wiki: no info Github: nothing checked-in / mentioned I'm sorry to say this, but from a version management/communicating this to the enduser point of view you dev guys suck. Why is it SOOO hart to change the download link to "Litecoin-Qt-0.8.6.2-SSL-fixed" on the official download page? [1]: of course I could build linking it against my own fixed version of openssl, but that's not the point.

Pages: « 1 2 3 4 5 6 7 8 9 10 [11]