 Show Posts
|
|
Pages: [1] 2 3 4 »
|
Just tried this tx on the website and it says it is already confirmed but it isn't  3a9b80a6a4f9229f18082e70f021441923262053bc20dc824090a78d60b8f306 Can you help? |
|
|
|
|
Does anyone know if the BTCP client will support multisig addresses? For example, with the BTC airdrop... will coins stored in multisig addresses be able to be claimed?
|
|
|
|
Hey walleting.services! Could you broadcast a bitcoin diamond transaction for me? My node is taking ages to sync, it has corrupted twice! EDIT: Just to let everyone know. Walleting.Services offered to send this tx for me. |
|
|
|
I have checked some address which I know had BTC in them at the time and none of them work in your address checking form.... https://www.semux.org/btc/ |
|
|
|
The distribution seems weird. Any reasons behind it?
This is UnitedBitcoinThank you for asking, yes are several reasons. Let me explain, UnitedBitcoin’ s fork breaks from convention with regards to distribution by differentiating between active- and inactive addresses. There are several advantages for doing so, first of all, it allows us to distribute UBTC across chains and across communities. Second, because there is less alt-coin flipping, resulting in less volatility for Bitcoin itself. Lastly, the remaining (inactive) balance can be used as collateral for future Eco-system developments. Except from the utterly stupid conditions regarding which addresses are inactive and which aren't. |
|
|
|
|
Does anyone have the super bitcoin wallet running and can broadcast a signed transaction for me?
EDIT: HarryPorter has obliged. Thanks!
|
|
|
|
Fantastic. I read a few things online that it wouldn't build. Will give it a go shortly.  |
|
|
|
|
Looking for a Bitcoin Diamond wallet that builds. Or a pre-built binary?
|
|
|
|
|
6f24945b71fd5214774b82ee4290a929094453e5cd165d55de38f93e0eb71c05
Could you help my friend out?
Thanks
|
|
|
|
|
I'd just like to say that I did a trade (0.0811 btc) with Kashish a couple of days ago and it went very smoothly.
|
|
|
|
|
Ok. For all those with transactions hashes that didn't appear in the blockchain (like me) I may have a solution.
Close simplewallet and the daemon
Delete your poolstate.bin (i moved mine instead of deleting just in case) - it's in the same place as the blockchain file
Restart the wallet and daemon
The balance should be back to normal and you should be able to resend the coins.
Thanks goes to fluffypony on IRC who suggested this.
|
|
|
|
Sent coins an hour ago, but can't find revived transaction id on blockchain sites. Why?
Same problem. Not sure what is going on. Same here. Got two transactions out fine and it's in mintpal. Another transaction is nowhere to be seen. |
|
|
|
Summercoin was dead, they change it to Summer2 and there is again some activity, we are so running behind, either EAC need to come with something that will really become a hype or we will hit 1 sat soon, pretty sad story for one of the biggest coins in the beginning of the year. Pretty sad.
This. Change to X11 or something. Not only is it more earth friendly, using less power, but it's an algo people like at the moment. Sort it out guys. |
|
|
|
Tried this, made no difference. I've tried PiMP, no difference. Some good news however... I've managed to get my cards hashing back at the same clocks with nearly the same hashrate. I did this by removing my undervolting. Anyone have any ideas on how this miner could've messed up the voltage on my cards? or if you can think of anything else that could have done it? I'm going to leave them hashing away like this for now, try and get it working stable. Then I'll tackle my undervolt again. It has been working for over 6 months perfectly fine before I used this (so it's not an unstable undervolt), very strange. Just a quick update for anyone that is interested/has any ideas. Thanks for all the suggestions so far guys, much appreciated |
|
|
|
The exact name is display driver uninstaller. DDU.
Yeah, that's the one I used. No difference sad times. |
|
|
|
|
Cleaned the driver, no change.
Going to have a go with PiMP to see if it's somehow knackered my GPUs or if its the OS. Downloading now.
|
|
|
|
patriot1889 you used "setx GPU_MAX_ALLOC_PERCENT 100" and now it is permamently saved in windows registry and others miners doesnt't accept it
now you will have to reinstall system or remove this keys from system registry
Hmm I used that a long time ago and mined most algos successfully after that, with many different drivers? Yes, Zembal, I have also used that before so I don't think that's it. But thanks for the suggestion I'll try driver cleaner and a reinstall. |
|
|
|
Argh. After mining with this miner I can't mine other algos any more. The drivers just crash. I managed to get them working again at lower clocks than I used to use. Anyone got any ideas whats going on?! |
|
|
|
Thanks for the reply. I quickly figured out that it was syncing but had to type "save" to actually save the blockchain. So I thought, hey, I'll download the blockchain.bin (like you just suggested) but it fails to open it and a lot of red text comes up about errors in some temporary files. 2014-Jun-10 22:31:41.265122 Loading blockchain...
2014-Jun-10 22:31:47.307467 ERROR C:\temp\monero\git-experimental\bitmonero-0.8.
8update-x64\src\common/boost_serialization_helper.h:82 Exception at [unserialize
_obj_from_file], what=input stream error
2014-Jun-10 22:31:47.313468 Can't load blockchain storage from file, generating
genesis block.
2014-Jun-10 22:31:47.410473 ERROR ..\..\src\cryptonote_core\blockchain_storage.c
pp:74 Failed to add genesis block to blockchain
2014-Jun-10 22:31:47.414474 ERROR ..\..\src\cryptonote_core\cryptonote_core.cpp:
119 Failed to initialize blockchain storage
2014-Jun-10 22:31:47.418474 ERROR ..\..\src\daemon\daemon.cpp:164 Failed to init
ialize core
2014-Jun-10 22:31:47.421474 Mining has been stopped, 0 finished
Thanks again guys. EDIT: I see the problem. I think I might have downloaded the OS X blockchain as I was going to use it on my mac first. Then changed my mind. Downloading the windows blockchain and will report back. EDIT2: Turns out I was wrong, I had the right blockchain. It still won't work EDIT3: Redownloaded the blockchain a third time and boom, works. Heh. |
|
|
|
|
