Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Proto

Pages: 1 [2] 3 4 5
16
Marketplace / Re: [WTB] 10000 PTS @.0072 BTC/PTS
« on: November 14, 2013, 01:39:24 pm »
I'm selling 600 PTS if you're still interested in buying: http://bitsharestalk.org/index.php?topic=614.0

17
Marketplace / Re: [WTB] 500 PTS @.008 BTC/PTS
« on: November 14, 2013, 01:38:00 pm »
I can also offer you 500 PTS, even 600 PTS if you want

18
Marketplace / Re: [WTS] 600 PTS. Please post your offers.
« on: November 14, 2013, 01:33:13 pm »
0.002 is a bit of a stretch. Current buy / sell prices are around 0.007 , 0.008 BTC per PTS

19
Marketplace / [WTS] 600 PTS. SOLD @ 0.007 BTC per PTS
« on: November 14, 2013, 12:22:35 pm »
I prefer offers for all 600 PTS at once, but any other quantity is also fine. I've already successfully sold 4500 PTS on this board to a handful of people.

20
I tried switching to the sphlib library for better sha512 performance, I seem to be getting about 50% more collisions per minute on my test system

I would be happy if someone could test how it affects their performance.
https://github.com/FrzMe/jhProtominer/tree/linux-port

10% more collisions on a 16 core (32 threads) machine.

21
BitShares PTS / Re: 1 BTC Bounty - Build Faster Miners People :)
« on: November 13, 2013, 03:34:12 pm »
An optimised miner not tied to any pool becomes very important now. Ypool has more than 50% of hashing power and that is not good for a decentralised currency!

22
Woha. Ypool now has coll/m: 1495296.00 and 50000 connected workers.

Actually that's very bad for Protoshares. Look at the overall stats. Looks like Ypool finds nearly every block there is and could pull off a 50% attack with ease. I know, there is no reason he should do it, because the 6% fee is quite lucrative and he will protect his investment. But still that is fundamentally not good for a crypto currency.

We need a solo miner with similar performance to level out the playing field and make this a decentralised currency again!

23
Some hints:

1. Rent a couple of cores from your favourite cloud provider (linux is usually cheapest).
2. Right now the fastest miner is jhProtominer. Its even much easier to compile and run than a Protoshares client, instructions are in the ypool thread.
3. Compile it on one machine, copy it to the others. Ypool takes quite a large cut (6%!), but his new miner is at least 2x faster than the newest stock client.

Profit margins are shrinking and I'm probably out on the next difficulty change, if the price doesn't move up significantly in the mean time.

24
Botnets?

Cloud mining. It's still profitable if you do it right.

25
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 07:29:28 pm »
Starting the client with the salvagewallet option + using a backup helped. Thanks!

A remainder to anyone here: MAKE BACKUPS

Does salvagewallet reimport all key pairs, even the unnamed ones? Not that I get into trouble when I try to spend some of that PTS (change address)

26
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 07:16:21 pm »
This happend to almost all of my protoshare-wallets, including the wallets on the miners.
I already started to dump the wallets using db_dump. 
Then I just tried the qt-client and the salvagewallet option.

Did you recover your PTS? What DB version are you using?

27
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 07:07:29 pm »
Only difference between my miners and my client wallet is the db version used.

My miners use:
libdb_cxx-4.7.so => /usr/lib64/libdb_cxx-4.7.so

The problematic client is linked against:
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so

To anyone with the same problem, please run ldd on your binary and report back what db version you used

28
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 07:03:12 pm »
Yes, I'm using the non qt-client. Nonetheless thanks, I will try loading my wallet.dat with a qt-client and report back. Have multiple backups, so I still have high hopes I didn't loose all that money. 

29
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 06:54:30 pm »
That really sucks :(
Private key export was also broken with the first version on git... so I didn't do it.
Any other way to extract the private key manually from wallet.dat, if I know the address?

30
BitShares PTS / Re: Corrupted wallet.dat
« on: November 12, 2013, 06:52:42 pm »
I don't use binaries for new alt-coins... I'm compiling from newest git source.
I have deleted everything except my wallet.dat and try to redownload the blockchain currently. Did a git pull and complete recompile.
I get lots of warnings:

ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
ERROR: mempool transaction missing input
...


Then after a while, with my backup wallet.dat:


*** System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
Error: System error: CDB() : can't open database file wallet.dat, error -30973
ERROR: AcceptBlock() : AddToBlockIndex failed
ProcessBlock: ACCEPTED
CreateNewBlock(): total size 1000
bitcoind: main.cpp:1662: bool CBlock::ConnectBlock(CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `pindex->pprev == view.GetBestBlock()' failed.
Aborted (core dumped)

Pages: 1 [2] 3 4 5