Pages:
Author

Topic: [ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC] - page 85. (Read 281383 times)

hero member
Activity: 1151
Merit: 528
Man, been hashing away with 5 per minute and found nothing in hours :/
member
Activity: 60
Merit: 10
I figure I'd ask again because I don't believe I ever got a reply - when I try to put any processes (1-4) set to mine this coin, it turns my ASICs into Zombies (which are mining bitcoin).  This has never happened with any coin I have ever mined; is there a potential reason for this?  
full member
Activity: 168
Merit: 100
I'll have a steak sandwich and a... steak sandwich
I can understand the reasoning behind transferring transactions from MemoryCoin 1.0 over to this block chain, but I don't understand the ProtoShares thing. If I own 100 PTS, I can import that wallet.dat and I get 10 MMC? Why?
sr. member
Activity: 356
Merit: 255
Mining block 295 since 30 minutes. I guess 296 will be mined in 1 minute, and 297 again in 30-60.

Yes, this difficulty algorithm is going to need to be addressed. I'm looking at options now.


even though i am empty handed, i think this should be left as is, the whole point of currency is that it should be scarce. The 10 PTS trade off is now justifiable. tampering with it at this point would discredit the honour system for those who did import some coins. 

I think instead focusing on an optimized miner may help distribution, maybe even a pool over the weekend.
Fixing the difficulty adjustment algo won't change the scarcity - it will make the difficulty adjustments more linear instead of hopping around so wildly. There's currently simply too few data points being used for the calculation, which skews the average badly. With more data points to calculate from, the curve will be much smoother and predictable. It won't (shouldn't) change the number of blocks per hour.
mux
sr. member
Activity: 280
Merit: 250
Mining block 295 since 30 minutes. I guess 296 will be mined in 1 minute, and 297 again in 30-60.

Yes, this difficulty algorithm is going to need to be addressed. I'm looking at options now.


What's fun is that with this difficulty algorithm, mining speed can be compared to the speed of a object in elliptic orbit trying to escape a planet attraction:
- On low orbit/high speed: motors at full throttle, accelerating (miners firing up mining machines, accelerating)
- On high orbit/low speed: motors shut down (miners shutting down machines, waiting for the more profitable high mining speed times).
And after each cycle, the elliptic nature of the orbit get more pronounced.

If the difficulty algorithm stays as it is now, I would forecast profitable mining periods of only 30 minutes every few days, and still spacing up =)
newbie
Activity: 11
Merit: 0
 ./bitcoind getinfo
{
    "version" : 85200,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 2.69230769,
    "blocks" : 240,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00000097,
    "testnet" : false,
    "keypoololdest" : 1387117140,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

after small time
./bitcoind getinfo
error: {"code":-1,"message":"CDB() : can't open database file wallet.dat, error -30974"}

...
legendary
Activity: 882
Merit: 1000
Mining block 295 since 30 minutes. I guess 296 will be mined in 1 minute, and 297 again in 30-60.

Yes, this difficulty algorithm is going to need to be addressed. I'm looking at options now.


even though i am empty handed, i think this should be left as is, the whole point of currency is that it should be scarce. The 10 PTS trade off is now justifiable. tampering with it at this point would discredit the honour system for those who did import some coins. 

I think instead focusing on an optimized miner may help distribution, maybe even a pool over the weekend.
sr. member
Activity: 771
Merit: 258
Trident Protocol | Simple «buy-hold-earn» system!
I get an error trying to load the client - it gets stuck on "Verifying Blocks..." stage and refuses to load. Anyone any idea what this is?
hero member
Activity: 724
Merit: 500
Mortimer, restart the client with the lower block count. It helped here.
hero member
Activity: 532
Merit: 500
OK, so I have the qt running on two machines . . .

Getmining info reads this one machine:

{
"blocks" : 295,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00001474,
"errors" : "",
"genproclimit" : 10,
"hashespermin" : 1.06024301,
"pooledtx" : 0,
"testnet" : false
}


And it reads this on the other machine:

{
"blocks" : 294,
"currentblocksize" : 1486,
"currentblocktx" : 2,
"difficulty" : 0.00001179,
"errors" : "",
"genproclimit" : 4,
"hashespermin" : 0.61135282,
"pooledtx" : 2,
"testnet" : false
}


Both clients  say they are synchtonized, what gives?  How can they be working on different blocks?  And at different difficulties?
legendary
Activity: 1428
Merit: 1030
Mining block 295 since 30 minutes. I guess 296 will be mined in 1 minute, and 297 again in 30-60.

Yes, this difficulty algorithm is going to need to be addressed. I'm looking at options now.
member
Activity: 99
Merit: 10
yea very strange is it just me or did difficulty spike for about 8x ?
hero member
Activity: 724
Merit: 500
Mining block 295 since 30 minutes. I guess 296 will be mined in 1 minute, and 297 again in 30-60.
member
Activity: 68
Merit: 10
"Imagination is more important than knowledge"
I can run the client under 32-bit (Windows 7), but I cannot run in mining mode since it crashes.

How much memory you got in those machines? what error are you getting?

The error just says to contact the dev team.
hero member
Activity: 724
Merit: 500
May the crashes somehow be related to the warning bitcoind gives out every time on start (Ubuntu linux)?

bitcoind: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by bitcoind)
bitcoind: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /lib/x86_64-linux-gnu/libssl.so.1.0.0)
bitcoind: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /lib/x86_64-linux-gnu/libssl.so.1.0.0)
bitcoind: /usr/local/lib/libcrypto.so.1.0.0: no version information available (required by /lib/x86_64-linux-gnu/libssl.so.1.0.0)

p.s.

A fork of the coin with averaging difficulty over 6 blocks may be a good idea.
newbie
Activity: 3
Merit: 0
Long time lurker first time poster, how would I know if I was on the correct MMC?  As I mined a block last night (which somehow woke me up from my sleep, must have been excited - fyi live in Australia) - I can't seem to find a block explorer to confirm the block I have is live/correct.  I have deleted all the database/files except wallet.dat and reloaded block chain, and re-downloaded the binary So I would assume I am on the correct version (2.0) however any way to tell?
full member
Activity: 462
Merit: 100
Who needs a pool when you have luck? Smiley
Just hit the jackpot (was missing the ding ding ding sound of a lot of coins dropping).
280.0103 MMC reward Smiley
(i7 Laptop with 2.5 h/m)
hero member
Activity: 658
Merit: 502
Why don't make a pool? Will be rich of your coin

This coin as born yesterday. Give to us to play in solo a little. Pools will arrive soon, don't worry.



FaSan

The problem its looks only born for the luckiest people around of the world xD 


And it's not good ? Better this than to rich people that can buy 1000 CPU :-)


FaSan
newbie
Activity: 11
Merit: 0

[/quote]

Okay - it would be helpful to have the debug.log following the crash - [email protected]

[/quote]

I'm sent email too.
mux
sr. member
Activity: 280
Merit: 250
given the difficulty how many hashes on average are needed to find a block?

You mean, how many luck you need?  Grin
Pages:
Jump to: