Search content
Sort by
Showing 20 of 52 results by Proteu5
Re: [ A N N ] RedOakCoin::{ R O C } Scrypt Currency By: RedOakIndustries [ R O I ]
Aetheros Here;
Updating To Public KGW Release Imminent!
Pending Final Review!
Prepare For Update.
Updating To Public KGW Release Imminent!
Pending Final Review!
Prepare For Update.
Prepare for LIFTOFF!
Re: [ A N N ] RedOakCoin::{ R O C } Scrypt Currency By: RedOakIndustries [ R O I ]
What's the point if wallet can't sync?
What OS are you on?Did you try the debug instructions posted several replies before?
Also try to port forward 7266 on your router, but this is last ditch effort.
Re: [ A N N ] RedOakCoin::{ R O C } Scrypt Currency By: RedOakIndustries [ R O I ]
http://i.imgur.com/BLXI0bD.png?1
Future Rode Map:(Development Critical)
Future Rode Map:(Development Experimental)
Future Rode Map:(Development Critical)
- RedOakIndustries Public Adaptation Of The, "RedOakCluster"
- RedOakIndustries: Recruitment & Membership Phase
- RedOakCluster IRC Channel
- RedOakCoin/RedOakCluster { Python | C++ : ( External-ROC:Core ) } Chat Protocol For clusterMembers & Dev., Op-Critical Discussions & Conceptualization
- RedOakCoin Android & iOS Wallet's
- RedOakCoin Lite-Wallet
Future Rode Map:(Development Experimental)
- Philanthropy Operations & Donation Efforts
- RedOakCoin:ROC Miner Integration (Public Information Pending ROI:Cluster Approval)
- (More To Be Released: Pending Public Announcement Approval)
"We have an interesting & exciting rode ahead of us! There is an entire database of projects, from Marketing and Psychological-Based Interest Projects to Hard-Developed Apps & Core-Additions!
We can not wait to see what the future has in store for all us; this is going to be so much fun!"
--Aetheros
We can not wait to see what the future has in store for all us; this is going to be so much fun!"
--Aetheros
After a person sent me a email. We have added Red Oak Coin to voting Please contact me about adding Red Oak coin on the exchange
Thank you, I am on my Personal Bitcointalk Account on my phone! I am heading to my classes soon (last yr. Of. College as psych major) I just wanted to let everyone know that we have several nodes coming online soon plus I have found and will cover personally a dedicated DNS Server.
This exchange news is great, and we have others in talks with us as well. If you are interested in running a node please let us know and post your addnode here!
I can't wait to check my emails and get my Team Breifs later today!
--Aetheros (a.k.a. Proteu5)
Re: [70 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
it is also true that it is just "gamblers law"
Well spotted! I was hoping nobody notices. 
However, we have DGM payouts at this pool, and this a non-linear thing. When you start mining, your DGM value takes some 100 hours to "fill up". After this your DGM for this round hardly increases anymore.
Imagine this round is going to finish in 100 hours, i.e. a 1100 hours round. If you started mining at the beginning of this round you'll have "wasted" 1000 hours. If you start now then you'll reach your maximum DGM value right on time. (I haven't done the maths, though. Could be this is still gambler's fallacy.)
A while back a proposed a system to payout devout & dedciated miners to avoid this issue on long blocks. However, seeing as though this is very one-track and single-minded, I may want to restate the idea with a modification. You can't reward people to avoid the problem you stated as we have seen that after a long block there can be a series of continuous short lived rounds. However, if there a dedicated time + dgm system it would have to kick in after a 5-round payout average: 5-Rounds post the long round if the miner's average to earning was not met, there could be a compensation in some way, shape or form. The compensation would still equal out to being much lower than 40% so as not to bankrupt the pool. However, as a very smart BTC member stated, my previous system left open the risk for a Block-Withholding attack.
I wish there was something we could do. However, I feel @mmpool is doing the right thing right now with managing this pool
Edit:
https://bitcointalk.org/index.php?topic=559011.msg6166821#msg6166821
[Original Post For Reference]
It's a good idea. I'm sure many of us are good at digital investigative work.
My only concern would be, speaking generally, the risks and your credibility.
Ie: I track down a bail jumper online only to find out the higheree just wanted to spy on his ex-girlfriend.
With that worry aside If I were to be contracted legally I would only feel comfortable accepting payment upon competition. So you would have to use an escrow service.
Nice idea.
My only concern would be, speaking generally, the risks and your credibility.
Ie: I track down a bail jumper online only to find out the higheree just wanted to spy on his ex-girlfriend.
With that worry aside If I were to be contracted legally I would only feel comfortable accepting payment upon competition. So you would have to use an escrow service.
Nice idea.
Looking to buy from either Canada or the Americas (minus US) one or one box of Cuban; Romeo Y Julieta cigars.
Must be a reputable seller or cost less than $25 so that I can assume all risk with confidence.
Must be a reputable seller or cost less than $25 so that I can assume all risk with confidence.
Re: [55 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
I'm missing so much on the thread!
I just finished updating my Android API-Monitor: 'LiteMonitor' and I finally added MMPool.
https://github.com/Proteu5/LiteMonitor
I originally made it for myself to check my stats at work and not deal with URL's and Apps, when i'm sneaking my phone haha. It's a work in progress, but does its job perfectly.
Coded in Python and needs Android App QPython; no extra libraries.
I just finished updating my Android API-Monitor: 'LiteMonitor' and I finally added MMPool.
https://github.com/Proteu5/LiteMonitor
I originally made it for myself to check my stats at work and not deal with URL's and Apps, when i'm sneaking my phone haha. It's a work in progress, but does its job perfectly.
Coded in Python and needs Android App QPython; no extra libraries.
Re: The genesis block is hurting my soul.. Please help [25 MegaCoin bounty]
Testing... seems wonderful! 
UPDATE:
I make this steps but when I open the client do not show the MerkleRoot that you say - The client will show an error but show the merkleroot. but I copy the Merkle that have on debug.log and now I will compile.. I will send news.
Thanks
NEW UPDATE - REASON: TESTS
http://i.imgur.com/wP8La8b.jpg
Why I receive this error?
My debug.log file:
Thanks
New Update - REASON: Other error
So, I've cleaned the Merkle and the Genesis to 0x and now I receive this message:
http://i.imgur.com/2oxYYI3.jpg
UPDATE:
Hi,
didn't read all the thread. But this will help you with Litecoin clients:
(this work only if you already did the basis (=change your timestamp, ntime, ect...) and ready to mine your merkle/genesis.)
- Open main.cpp
- Go to "bool InitBlockIndex()"
- Search "block.print();"
- ABOVE, you copy this:
This is a script that doing all the annoying job for you.
How to use it ?
- First you need to empty your merkleroot, genesis and nnonce (merkle = "0x", genesis="0x", nonce=0.
- Then you compil and start the client.
- The client will show an error but show the merkleroot.
- Now change you merkle root variable for your new one.
- Compil again and start again.
- Your client will try to mine your genesis block, this operation can be very fast as she can be very slow.
- After this, the client will show again an error but give you the genesis (gethash) and nonce.
- reopen your client script, change the genesis and nonce (and verify your ntime).
- REMOVE the script I gave you (or comment).
- Compil and enjoy
I don't know if someone got the bounty, but i'm not looking after, just helping =)
didn't read all the thread. But this will help you with Litecoin clients:
(this work only if you already did the basis (=change your timestamp, ntime, ect...) and ready to mine your merkle/genesis.)
- Open main.cpp
- Go to "bool InitBlockIndex()"
- Search "block.print();"
- ABOVE, you copy this:
Code:
// This part was used to generate the genesis block.
// Uncomment to use it again.
// If genesis block hash does not match, then generate new genesis hash.
if (true && block.GetHash() != hashGenesisBlock)
{
printf("Searching for genesis block...\n");
// This will figure out a valid hash and Nonce if you're
// creating a different genesis block:
uint256 hashTarget = CBigNum().SetCompact(block.nBits).getuint256();
uint256 thash;
char scratchpad[SCRYPT_SCRATCHPAD_SIZE];
loop
{
#if defined(USE_SSE2)
// Detection would work, but in cases where we KNOW it always has SSE2,
// it is faster to use directly than to use a function pointer or conditional.
#if defined(_M_X64) || defined(__x86_64__) || defined(_M_AMD64) || (defined(MAC_OSX) && defined(__i386__))
// Always SSE2: x86_64 or Intel MacOS X
scrypt_1024_1_1_256_sp_sse2(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#else
// Detect SSE2: 32bit x86 Linux or Windows
scrypt_1024_1_1_256_sp(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#endif
#else
// Generic scrypt
scrypt_1024_1_1_256_sp_generic(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#endif
if (thash <= hashTarget)
break;
if ((block.nNonce & 0xFFF) == 0)
{
printf("nonce %08X: hash = %s (target = %s)\n", block.nNonce, thash.ToString().c_str(), hashTarget.ToString().c_str());
}
++block.nNonce;
if (block.nNonce == 0)
{
printf("NONCE WRAPPED, incrementing time\n");
++block.nTime;
}
}
printf("block.nTime = %u \n", block.nTime);
printf("block.nNonce = %u \n", block.nNonce);
printf("block.GetHash = %s\n", block.GetHash().ToString().c_str());
}
// Uncomment to use it again.
// If genesis block hash does not match, then generate new genesis hash.
if (true && block.GetHash() != hashGenesisBlock)
{
printf("Searching for genesis block...\n");
// This will figure out a valid hash and Nonce if you're
// creating a different genesis block:
uint256 hashTarget = CBigNum().SetCompact(block.nBits).getuint256();
uint256 thash;
char scratchpad[SCRYPT_SCRATCHPAD_SIZE];
loop
{
#if defined(USE_SSE2)
// Detection would work, but in cases where we KNOW it always has SSE2,
// it is faster to use directly than to use a function pointer or conditional.
#if defined(_M_X64) || defined(__x86_64__) || defined(_M_AMD64) || (defined(MAC_OSX) && defined(__i386__))
// Always SSE2: x86_64 or Intel MacOS X
scrypt_1024_1_1_256_sp_sse2(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#else
// Detect SSE2: 32bit x86 Linux or Windows
scrypt_1024_1_1_256_sp(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#endif
#else
// Generic scrypt
scrypt_1024_1_1_256_sp_generic(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
#endif
if (thash <= hashTarget)
break;
if ((block.nNonce & 0xFFF) == 0)
{
printf("nonce %08X: hash = %s (target = %s)\n", block.nNonce, thash.ToString().c_str(), hashTarget.ToString().c_str());
}
++block.nNonce;
if (block.nNonce == 0)
{
printf("NONCE WRAPPED, incrementing time\n");
++block.nTime;
}
}
printf("block.nTime = %u \n", block.nTime);
printf("block.nNonce = %u \n", block.nNonce);
printf("block.GetHash = %s\n", block.GetHash().ToString().c_str());
}
This is a script that doing all the annoying job for you.
How to use it ?
- First you need to empty your merkleroot, genesis and nnonce (merkle = "0x", genesis="0x", nonce=0.
- Then you compil and start the client.
- The client will show an error but show the merkleroot.
- Now change you merkle root variable for your new one.
- Compil again and start again.
- Your client will try to mine your genesis block, this operation can be very fast as she can be very slow.
- After this, the client will show again an error but give you the genesis (gethash) and nonce.
- reopen your client script, change the genesis and nonce (and verify your ntime).
- REMOVE the script I gave you (or comment).
- Compil and enjoy
I don't know if someone got the bounty, but i'm not looking after, just helping =)
I make this steps but when I open the client do not show the MerkleRoot that you say - The client will show an error but show the merkleroot. but I copy the Merkle that have on debug.log and now I will compile.. I will send news.
Thanks
NEW UPDATE - REASON: TESTS
http://i.imgur.com/wP8La8b.jpg
Why I receive this error?
My debug.log file:
Code:
2014-04-11 18:44:00
2014-04-11 18:44:00 XXX version v0.8.6.2-g10d589b-beta (Thu, 3 Apr 2014 21:58:44 -1000)
2014-04-11 18:44:00 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-04-11 18:44:00 Default data directory C:\Users\Leandro\AppData\Roaming\XXX
2014-04-11 18:44:00 Using data directory C:\Users\Leandro\AppData\Roaming\XXX
2014-04-11 18:44:00 Using at most 125 connections (2048 file descriptors available)
2014-04-11 18:44:00 Using 2 threads for script verification
2014-04-11 18:44:00 init message: Verificando carteira...
2014-04-11 18:44:00 dbenv.open LogDir=C:\Users\Leandro\AppData\Roaming\XXX\database ErrorFile=C:\Users\Leandro\AppData\Roaming\XXX\db.log
2014-04-11 18:44:00 Bound to [::]:25991
2014-04-11 18:44:00 Bound to 0.0.0.0:25991
2014-04-11 18:44:00 init message: Carregando índice de blocos...
2014-04-11 18:44:00 Opening LevelDB in C:\Users\Leandro\AppData\Roaming\XXX\blocks\index
2014-04-11 18:44:00 Opened LevelDB successfully
2014-04-11 18:44:00 Opening LevelDB in C:\Users\Leandro\AppData\Roaming\XXX\chainstate
2014-04-11 18:44:00 Opened LevelDB successfully
2014-04-11 18:44:00 LoadBlockIndexDB(): last block file = 0
2014-04-11 18:44:00 LoadBlockIndexDB(): transaction index disabled
2014-04-11 18:44:00 Initializing databases...
2014-04-11 18:44:00 b103277b47c133eeb6b58486d9bec984dee754bfda81010844221637e58113b9
2014-04-11 18:44:00 0000000000000000000000000000000000000000000000000000000000000000
2014-04-11 18:44:00 53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29
2014-04-11 18:44:00 CBlock(hash=b103277b47c133eeb6b58486d9bec984dee754bfda81010844221637e58113b9, input=010000000000000000000000000000000000000000000000000000000000000000000000298a6f76913c06f26c3a0b57a7f59f72fd553bb9901529e0324bc43ffd4ce55399004853f0ff0f1e00000000, PoW=daf38cbceaac5a570916ae3b11bcb32ce288631677bad01fe41b54978af520ba, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29, nTime=1397227673, nBits=1e0ffff0, nNonce=0, vtx=1)
2014-04-11 18:44:00 CTransaction(hash=53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 04ffff001d010444323031342f30342f313120427564676574204368696566204973204f62616d61e28099732043686f696365206173204e6577204865616c7468205365637265746172792e)
CTxOut(nValue=3.00000000, scriptPubKey=04678afdb0fe5548271967f1a67130)
vMerkleTree: 53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29
2014-04-11 18:44:00 XXX version v0.8.6.2-g10d589b-beta (Thu, 3 Apr 2014 21:58:44 -1000)
2014-04-11 18:44:00 Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
2014-04-11 18:44:00 Default data directory C:\Users\Leandro\AppData\Roaming\XXX
2014-04-11 18:44:00 Using data directory C:\Users\Leandro\AppData\Roaming\XXX
2014-04-11 18:44:00 Using at most 125 connections (2048 file descriptors available)
2014-04-11 18:44:00 Using 2 threads for script verification
2014-04-11 18:44:00 init message: Verificando carteira...
2014-04-11 18:44:00 dbenv.open LogDir=C:\Users\Leandro\AppData\Roaming\XXX\database ErrorFile=C:\Users\Leandro\AppData\Roaming\XXX\db.log
2014-04-11 18:44:00 Bound to [::]:25991
2014-04-11 18:44:00 Bound to 0.0.0.0:25991
2014-04-11 18:44:00 init message: Carregando índice de blocos...
2014-04-11 18:44:00 Opening LevelDB in C:\Users\Leandro\AppData\Roaming\XXX\blocks\index
2014-04-11 18:44:00 Opened LevelDB successfully
2014-04-11 18:44:00 Opening LevelDB in C:\Users\Leandro\AppData\Roaming\XXX\chainstate
2014-04-11 18:44:00 Opened LevelDB successfully
2014-04-11 18:44:00 LoadBlockIndexDB(): last block file = 0
2014-04-11 18:44:00 LoadBlockIndexDB(): transaction index disabled
2014-04-11 18:44:00 Initializing databases...
2014-04-11 18:44:00 b103277b47c133eeb6b58486d9bec984dee754bfda81010844221637e58113b9
2014-04-11 18:44:00 0000000000000000000000000000000000000000000000000000000000000000
2014-04-11 18:44:00 53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29
2014-04-11 18:44:00 CBlock(hash=b103277b47c133eeb6b58486d9bec984dee754bfda81010844221637e58113b9, input=010000000000000000000000000000000000000000000000000000000000000000000000298a6f76913c06f26c3a0b57a7f59f72fd553bb9901529e0324bc43ffd4ce55399004853f0ff0f1e00000000, PoW=daf38cbceaac5a570916ae3b11bcb32ce288631677bad01fe41b54978af520ba, ver=1, hashPrevBlock=0000000000000000000000000000000000000000000000000000000000000000, hashMerkleRoot=53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29, nTime=1397227673, nBits=1e0ffff0, nNonce=0, vtx=1)
2014-04-11 18:44:00 CTransaction(hash=53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 04ffff001d010444323031342f30342f313120427564676574204368696566204973204f62616d61e28099732043686f696365206173204e6577204865616c7468205365637265746172792e)
CTxOut(nValue=3.00000000, scriptPubKey=04678afdb0fe5548271967f1a67130)
vMerkleTree: 53e54cfd3fc44b32e0291590b93b55fd729ff5a7570b3a6cf2063c91766f8a29
Thanks
New Update - REASON: Other error
So, I've cleaned the Merkle and the Genesis to 0x and now I receive this message:
http://i.imgur.com/2oxYYI3.jpg
Your missing a step from the guide, re-read it closely. Just mind you, if you intent to release a coin; know that it will change your life - don't take short cuts, and always be professional (my 2 cents) That being said...You need to populate your 0x lines after error one.
1) Restart
2) New TimeStamp
3) 0x
4) Error
5) Populate
6) Follow guide
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
How much BTC/MHS/DAY getting from this merged pool?
Over a long enough time you should expect the same BTC/MHS/DAY rate from all pools minus their fees. The difference with mmpool is that hashrate is currently low enough that you may go days without payment and then get a big payment all at once.
Mmpools newly added PPS for BTC is a nice little bonus, bit without even factoring that into my decision for using them, their DGM payment method has to be my favorite. Yes, you won't get a payout daily, but when you do, like @TechByPC said, its a very handsome payout.
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
5% is still okay in my book, but that's about the limit. LiteGuardian does 2% PPS, and it's not doing any hybrid.
The reserves a pool needs to handle the swings of PPS are too much for it to be a consideration. Combine that with the block withholding attack risk that can drive the pool bankrupt it's not worth it.I like mmpool with or without PPS, I'm just giving my opinion on PPS in general.
Oh, well yea, I agreed with you 100% with PPS in general.
Personally, I think PPS rates should be trailing; based on the pool's average rate at which they find blocks for one Difficulty Term.
I would first set my break-even, minimum PPS %, then choose an arbitrary number + % as the first control term. After the Network Difficulty adjusts, get the avg. Time between blocks on network and between blocks found in pool. I would see how the pools avg. Hashrate changed +/- then adjust the PPS n% higher, or lower.
Of course you would need an upper bound limit pool miners would agree too, but adjusting the PPS between let's say 1.25% and 5.05% could average out nicely for Pool managers and Devoted Miners.
My math is 'Pseudo Math' I would need time to write an actual formula, but that's my idea.
PPS with a variable fee based on luck. Interesting.
Why would people withhold blocks, though? I mean, it doesn't hurt them, but it doesn't help them in any way, either. It's just being a dick.
Exactly what I thought.
What I came up with, and this is still accepting 'Block Withholding' as a non-issue for the time being, would make use of Miner's Time On Pool as @kjlimo stated. You would calculate the PPS system using a SINC function (The SINE Wave Graphs). In order to determine PPS the pool uses a Singal-To-Noise formula to reduces 'noise' in the Sinc-Wave or Hashrate Fluctuations; this would find a % adjustment for each individual miner's PPS. The adjustment would be bound to the Upper and Lower limits being determined by the original idea I had. In addition each miner's time needs to be pitted up against their hashrate vs. pool hashrate (This I am still working on)...
What we have would be:
-Global 'Luck' calculations
- Upper Bound & Lower Bound Limits
- A Running & Adjusting SINC-Function
- Measuring Pool's Averages Dependent On The Global Variables
- Signal-To-Noise Recalculations
- Pushing The Sine Waves Higher or Lower to reach a median
- Be the medium 5% higher than the true median or 1% lower than true; etc.
- Individual Miner 'Variance' Calculations
- Comprised of Time On Pool
- & Value Or Total Shares
(Might Be Bad)- Miner Variance Gives a +/- above or below the Pool's [(Calculated)(Re-Adjusted[ing]) PPS-SINC Function]
I feel like I'm off somewhere :/
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
5% is still okay in my book, but that's about the limit. LiteGuardian does 2% PPS, and it's not doing any hybrid.
The reserves a pool needs to handle the swings of PPS are too much for it to be a consideration. Combine that with the block withholding attack risk that can drive the pool bankrupt it's not worth it.I like mmpool with or without PPS, I'm just giving my opinion on PPS in general.
Oh, well yea, I agreed with you 100% with PPS in general.
Personally, I think PPS rates should be trailing; based on the pool's average rate at which they find blocks for one Difficulty Term.
I would first set my break-even, minimum PPS %, then choose an arbitrary number + % as the first control term. After the Network Difficulty adjusts, get the avg. Time between blocks on network and between blocks found in pool. I would see how the pools avg. Hashrate changed +/- then adjust the PPS n% higher, or lower.
Of course you would need an upper bound limit pool miners would agree too, but adjusting the PPS between let's say 1.25% and 5.05% could average out nicely for Pool managers and Devoted Miners.
My math is 'Pseudo Math' I would need time to write an actual formula, but that's my idea.
PPS with a variable fee based on luck. Interesting.
Good points. I wish I could record my thoughts. I've got some ideas, and will work something out tomorrow...
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
Updated my email/sms/auto cashout/monitor helper site to use the new mmpool.org domain now. looks like everything working well, https://bitmonitor.usr.io/
Wow, nice! This is brilliant and very useful.@Mmpool, I honestly love your pool! I have new miners in the the mail, on their way. I'm hoping they arrive today 😊
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
OMG we found a block! Pending at the moment, will confirm shortly.
Edit: Block confirmed and available for withdrawal.
Hell Yeaaa!Edit: Block confirmed and available for withdrawal.
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
I'm rather new only having about 3 weeks of experience, I looked over many different pools and I liked the idea of the merged mining. I think I would like to see a few more coins added if they can be, I know many out there are worthless, but then a few years ago bitcoin wasn't worth the paper it was printed on either.
Is this round taking so long due to an increase in difficulty or just bad luck?
Is this round taking so long due to an increase in difficulty or just bad luck?
The merged Alt-Coins payout fine right now, and if you haven't, you should really look into Namecoin and Devcoin. NMC can act as a decentralized DNS and much more.
However, I've seen long rounds like this before, it could easily be difficulty. Normally, I've seen 9hr rounds and less, and been through a few other long ones as well.
It's worth it though. Plus the Dev. Is really nice and takes good care of the pool.
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
5% is still okay in my book, but that's about the limit. LiteGuardian does 2% PPS, and it's not doing any hybrid.
The reserves a pool needs to handle the swings of PPS are too much for it to be a consideration. Combine that with the block withholding attack risk that can drive the pool bankrupt it's not worth it.I like mmpool with or without PPS, I'm just giving my opinion on PPS in general.
Oh, well yea, I agreed with you 100% with PPS in general.
Personally, I think PPS rates should be trailing; based on the pool's average rate at which they find blocks for one Difficulty Term.
I would first set my break-even, minimum PPS %, then choose an arbitrary number + % as the first control term. After the Network Difficulty adjusts, get the avg. Time between blocks on network and between blocks found in pool. I would see how the pools avg. Hashrate changed +/- then adjust the PPS n% higher, or lower.
Of course you would need an upper bound limit pool miners would agree too, but adjusting the PPS between let's say 1.25% and 5.05% could average out nicely for Pool managers and Devoted Miners.
My math is 'Pseudo Math' I would need time to write an actual formula, but that's my idea.
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining/tor
5% is still okay in my book, but that's about the limit. LiteGuardian does 2% PPS, and it's not doing any hybrid.
The reserves a pool needs to handle the swings of PPS are too much for it to be a consideration. Combine that with the block withholding attack risk that can drive the pool bankrupt it's not worth it.I love mmpool with out PPS, the fact that OP even added it is really wonderful. Just saying...
ok I will check that out the USB hub is a cheap on so I start with that. I just wanna make sure that the config is ok as is.
http://s26.postimg.org/92fkd6gk5/IMG_20140406_135500.jpg
So many people in the web are just assuming and guessing I was reading thru the readme and made the jump in the cold water by getting the newest version where other people say dont get the new one stay with 3.1.1 because everybody is using that one. Please let me know if u want me to add or remove more from the config file. Thank you very much to both of you and I keep u posted about the usb hub results
http://s26.postimg.org/92fkd6gk5/IMG_20140406_135500.jpg
So many people in the web are just assuming and guessing I was reading thru the readme and made the jump in the cold water by getting the newest version where other people say dont get the new one stay with 3.1.1 because everybody is using that one. Please let me know if u want me to add or remove more from the config file. Thank you very much to both of you and I keep u posted about the usb hub results
Personally, I never use *.conf -- I always use *.bat files or *.sh files to run CG/BFG-Miner. You should be able to call a *.sh file on PI with terminal. Just input your commands, save as .sh, right click - properties - allow executable (or +x chmod), then run that file. First rename or .conf so it doesn't use it.
I know 3.1.1 still has Scrypt support and that is one main reason why people still use it. I am 1 step from compiling and testing the newest CGMiner if it wasn't for MingW and windows ridiculous dependency linking structure.
- Create New Text-File
- Save As Name.sh
- Set Executable
- Move into CGminer Root or put the address of CGminer root in the first line
- ./cgminer or cd /home/use/cgminer/
- If -or- then type below it ./cgminer
- Your next line will simply be your input command line
I've been working on a Linux program to organize *.conf files for mining different coins and using different settings. It gets messy when you have 20 *.sh files or 20 *.conf files.
Re: [47 TH] mmpool.org - 1.5% fee split DGM/PPS - tx fees/vardiff/merge mining
The minimum withdrawal amount for bitcoin has been lowered to 0.005 BTC from 0.01 BTC.
Nice!! Loving MMpool.org. Really has been one of my favorite BTC Pools for a long time
Just solved the issue:
Add to your CFLAGS
That solved the timeEndPeriod for me. Also, have you used the edit?
I am building 4.2.2 and with less settings but did encounter the same issues. My last build had zero errors but wouldn't run. If I discover anything that could help you I'll post or edit my post.
Edit:Sorry I'm also assuming you've made all necessary changes: such as -lcurl -lcurldll to libcurl.pc
**Throws Hands In The Air** I'm compiling with no errors and it still or won't run or I'm getting _WIN32.... already redifined >> When I fix this I get timeradd errors...
CFLAGS="-O2 -msse2 -DWIN32_LEAN_AND_MEAN -lws2_32 -lshlwapi -lmswsock" ./configure --enable-icarus
Add to your CFLAGS
Code:
-DWIN32
That solved the timeEndPeriod for me. Also, have you used the edit?
I am building 4.2.2 and with less settings but did encounter the same issues. My last build had zero errors but wouldn't run. If I discover anything that could help you I'll post or edit my post.
Edit:Sorry I'm also assuming you've made all necessary changes: such as -lcurl -lcurldll to libcurl.pc
**Throws Hands In The Air** I'm compiling with no errors and it still or won't run or I'm getting _WIN32.... already redifined >> When I fix this I get timeradd errors...
CFLAGS="-O2 -msse2 -DWIN32_LEAN_AND_MEAN -lws2_32 -lshlwapi -lmswsock" ./configure --enable-icarus
Code:
Minimum system required Minimum value for _WIN32_WINNT and WINVER
Windows 8.1 _WIN32_WINNT_WINBLUE (0x0602)
Windows 8 _WIN32_WINNT_WIN8 (0x0602)
Windows 7 _WIN32_WINNT_WIN7 (0x0601)
Windows Server 2008 _WIN32_WINNT_WS08 (0x0600)
Windows Vista _WIN32_WINNT_VISTA (0x0600)
Windows Server 2003 with SP1, Windows XP with SP2 _WIN32_WINNT_WS03 (0x0502)
Windows Server 2003, Windows XP _WIN32_WINNT_WINXP (0x0501)
Windows 8.1 _WIN32_WINNT_WINBLUE (0x0602)
Windows 8 _WIN32_WINNT_WIN8 (0x0602)
Windows 7 _WIN32_WINNT_WIN7 (0x0601)
Windows Server 2008 _WIN32_WINNT_WS08 (0x0600)
Windows Vista _WIN32_WINNT_VISTA (0x0600)
Windows Server 2003 with SP1, Windows XP with SP2 _WIN32_WINNT_WS03 (0x0502)
Windows Server 2003, Windows XP _WIN32_WINNT_WINXP (0x0501)