 Show Posts
|
|
Pages: [1]
|
|
I must say that a lot of people do not know how to build gominer resulting in them looking for binaries through other sources.
I'll start publishing binaries when the current development version turns out to be stable.
|
|
|
|
Attention GO miner SIA has a serious vulnerability, it allows an attacker to remotely monitor mining on computers and redirecting the transaction in your wallet and in the wallet of the attacker. In detail, I could be wrong, but the circumstances are about.
Ask yourself the question of why the unknown speed of the network is SIA? Think about the type of algorithm. Who can it be profitable? .... large manipulations.
Seriously dude, gominer is open source and the reason there are no binaries released is exactly to prevent stupid statements like this. Read through the code yourself, it are only a few files in go code and validate yourself that the above statement is bullshit. |
|
|
|
I'm also missing the voting option for "pulling the plug". projects fail sometimes, that's life.
That option has always been there: sell your clams and don't look back. |
|
|
|
|
I agree, that would be the easiest thing, no more digging after a specific block.
If this is not an option, burning clams for doog seems reasonable as well.
|
|
|
|
why clam wallet show virus when scanned with virustotal
Clams is pretty addictive, smart scanner |
|
|
|
I can't seem to find that folder. I revealed hidden folders as well.  On OS 10.7.5 In Finder use the cmd+Shift+g keycombination and go to ~/Library/Application Support/ |
|
|
|
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(5f78f18bfb, 1), 1421669840) for block 2e91696a0657ae4df6f4abe26f90f473f8db447954b569be274a0b6f5938d1e1
Is on my todo list to investigate further. It might have to do with orphaned branches. For now, fastest way to go ahead is to resync. Empty the ~/Library/Application\ Support/Clam folder EXCEPT the wallet.dat put http://s3.amazonaws.com/dooglus/bootstrap.dat in the folder as well You can also copy the entire folder from a different wallet you have somewhere too (be sure to backup your wallet.dat). |
|
|
|
It seems like my client is perpetually out of synch now.  However it says I have 26 active connections and I can see the activity. I have one orphaned coin sitting at 1 confirmation for several hours. I hit the faucet to test and what usually goes right in the wallet seems like it's stuck in the blockchain as well. Running Mac Client 1.4.4 Thanks!  /s/ Can you look at the debug log (Console->Information->"Open" under Debug log file) to see what block it is stuck at? |
|
|
|
Any idea? In my wallet 4 stacks 4.6 clams each
and 6 days no stacking rewards.
Wallet say:
Your weight is 20
Network weight 42927482561401
Expected time is 9942 days.
I think something wrong or not?
Thank You
Upgrade to the latest binaries (1.4.4), it should give a real estimate now. |
|
|
|
Ya, I had a similar problem with my Clam Mac Client. For me, it saw the Clams on restart, however as I was on support chat with Clam tech, he said "Rescan". But alas, I found a hefty amount of Clam and I need not rescan. It's worth it.
I actually mined 5 coins since that time. Having missed out on the mining phase of crypto so last year, finding an extra coin in my client in the morning is quite rewarding!
Glad to hear you like Clam and the Mac client. It will be officially released soon. |
|
|
|
maybe someone give me some donate  You can buy them on polo, cryptsy,... |
|
|
|
Thanks Allejuppa, deleting the style.qss file worked a charm.  Glad to hear that, certainly don't hesitate to report any issues you encounter. Hopefully it can get released shortly. |
|
|
|
Can the blockchain be copied over from the Windows client, or must it be completely downloaded again?
I've honestly never tired... but I would suspect yes. I'll try myself later this evening I've just installed the new CLAM Wallet on MacOSX Yosemite. I loaded the application and it started to download the blockchain. I closed the client and then I was able to copy across the blockchain and wallet from my Windows machine. Files were copied from Windows (%appdata%\Clam) to MacOSX (~/Library/Application Support/Clam). I restarted the client after the copy was complete and the blockchain and wallet were available and in sync. The only thing I had to change in the new client was to stop using the black visual theme (under Options => Display) so that I could see the mouseover text for the locked/encrypted, staking, network connections, up to date icons (in the bottom left of the window). When using the black visual theme, the transparency was hard to read. I tried it against my dark wallpaper/background and against a light background but it didn't really make a difference. I do like the black theme but I can't use it atm. You should not have copied over the style.qss file. Delete that one and you should be good. Thanks for testing! |
|
|
|
|
