Topic: [ANN][OC] Orangecoin ★★ POS ★★ Anon Transactions ★★ Masternodes - page 28. (Read 209551 times)
price has slowly been rising last months.
hi, can someone tell me which algo use this coin?
thanks
thanks
OC is a 100% PoS coin.
hi, can someone tell me which algo use this coin?
thanks
thanks
Hi, I'm not sure where your "Roaming folder" equivalent would be, I'm a windows user. If you google search, you can find out where you can find your wallet.dat file is located and that's where your .conf should go.
Quick search results:
https://bitcointalksearch.org/topic/where-is-walletdat-file-path-in-mac-osx-lion-36542
http://bitcoin.stackexchange.com/questions/1350/where-is-bitcoin-information-wallet-dat-stored-on-os-x
Here's my .conf
addnode=54.235.70.55:18872
addnode=54.235.244.167:18872
addnode=167.114.27.243:18872
addnode=92.222.24.66:18872
addnode=1.34.180.245:18872
addnode=213.162.108.2:18872
addnode=73.33.254.6:18872
addnode=88.102.206.204:18872
Quick search results:
https://bitcointalksearch.org/topic/where-is-walletdat-file-path-in-mac-osx-lion-36542
http://bitcoin.stackexchange.com/questions/1350/where-is-bitcoin-information-wallet-dat-stored-on-os-x
Here's my .conf
addnode=54.235.70.55:18872
addnode=54.235.244.167:18872
addnode=167.114.27.243:18872
addnode=92.222.24.66:18872
addnode=1.34.180.245:18872
addnode=213.162.108.2:18872
addnode=73.33.254.6:18872
addnode=88.102.206.204:18872
Can anyone give some guidance on how to synch with the network? I am on a Mac and have been having trouble getting my client to synch and don't really know where to start. Do I have to add the .conf file somewhere? Thanks, any advice would be appreciated.
CF: 226118.097952
Edit: By the way I re-named the fund.
Edit: By the way I re-named the fund.
April 29, 2015, 12:58:10 AM
Alright, digging in the git provided me with this:
This tells me that for whatever reason, it's one year time limit that had to elapse for this error message to display. On what grounds? Idk yet.
Here's the definition for "IsSyncCheckpointTooOld":
Seems that's it's still based on the time elapsed. This is where I start to lose my grip on code. I can't go any farther with this without looking up the commands and directives in a c++ "dictionary".
But GOOD news! If it's taken a year to fulfill this, then it's not due to a lack in securiy via PoS difficulty. I'm guessing that OCdev intended for the network to be strong enough by now that we wouldn't need checkpoints. Checkpoints are NOT a necessity, but are helpful when syncing or if there are forks. No worries. Press on. New dev will be alerted to this to provide a fix, but my opinion: it's nothing to worry about for now.
Code:
if (Checkpoints::IsSyncCheckpointTooOld(60 * 60 * 24 * 365) && !fTestNet && !IsInitialBlockDownload())
{
nPriority = 100;
strStatusBar = "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
This tells me that for whatever reason, it's one year time limit that had to elapse for this error message to display. On what grounds? Idk yet.
Here's the definition for "IsSyncCheckpointTooOld":
Code:
bool IsSyncCheckpointTooOld(unsigned int nSeconds)
{
LOCK(cs_hashSyncCheckpoint);
// sync-checkpoint should always be accepted block
assert(mapBlockIndex.count(hashSyncCheckpoint));
const CBlockIndex* pindexSync = mapBlockIndex[hashSyncCheckpoint];
return (pindexSync->GetBlockTime() + nSeconds < GetAdjustedTime());
}
Seems that's it's still based on the time elapsed. This is where I start to lose my grip on code. I can't go any farther with this without looking up the commands and directives in a c++ "dictionary".
But GOOD news! If it's taken a year to fulfill this, then it's not due to a lack in securiy via PoS difficulty. I'm guessing that OCdev intended for the network to be strong enough by now that we wouldn't need checkpoints. Checkpoints are NOT a necessity, but are helpful when syncing or if there are forks. No worries. Press on. New dev will be alerted to this to provide a fix, but my opinion: it's nothing to worry about for now.
April 28, 2015, 06:46:40 PM
I haven't had the chance to find out from our code what the deal is, BUT I was given a solution if our code is no longer good.
https://github.com/baldurodinsson/auroracoin-project/tree/master/src
Still requires a dev, but my friend told me:
"There was automatic checkpointing code put in. Essentially, it added checkpoints without having to hard code them. It's on a very old codebase, but you might be able to implement something like that on OC. That would solve the issue in the long term, but a short term remedy would be hardcoding a checkpoint in the code and re-releasing wallets. Either way, it will take some coding, but the checkpoint hardcode is much easier to do."
Old code base to me is fine to rip things from, checkpoints are pretty basic and probably wouldn't change often - to date.
Now, I'm not exactly sure what we'd need to change in this to make it fit OC, and I'm not sure what other files in the git have to change to accept the checkpoint coding.
I still need to have a deep look into the OC code to see what I can do/find about our current checkpoints. Until tomorrow, or later tonight folks.
https://github.com/baldurodinsson/auroracoin-project/tree/master/src
Still requires a dev, but my friend told me:
"There was automatic checkpointing code put in. Essentially, it added checkpoints without having to hard code them. It's on a very old codebase, but you might be able to implement something like that on OC. That would solve the issue in the long term, but a short term remedy would be hardcoding a checkpoint in the code and re-releasing wallets. Either way, it will take some coding, but the checkpoint hardcode is much easier to do."
Old code base to me is fine to rip things from, checkpoints are pretty basic and probably wouldn't change often - to date.
Now, I'm not exactly sure what we'd need to change in this to make it fit OC, and I'm not sure what other files in the git have to change to accept the checkpoint coding.
I still need to have a deep look into the OC code to see what I can do/find about our current checkpoints. Until tomorrow, or later tonight folks.
April 28, 2015, 06:24:02 PM
Great!! Thanks for looking into this.
April 28, 2015, 04:49:56 PM
I did some asking around, our network is not vulnerable. Our difficulty is very strong when compared against a coin like TAG's PoS difficulty, granted they have PoW to pull out the forks. All explorers are matching when compared to the wallet. So since everything is fine, it's just a warning that we have an old checkpoint. I'm working on getting info to check the git to see if checkpoints are coded as a limited-time feature, or if it's destined to create another checkpoint.
April 28, 2015, 03:37:54 PM
Probably a simple fix, but then you know we have problem of no dev.
April 27, 2015, 11:32:00 AM
anybody getting this error this just started happening.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
I am guessing it has to do with OC being 1 year old, but I really don't know. I'm still staking so it's ok?? I'm really not sure. Leave your wallets online until we get a fix. I know other ppl have this message, too.
It's only minor problem right now. Checkpoints are needed for the network to agree on the blockchain, for forks. But it's time to get a dev over here.
I quote from this reddit: http://www.reddit.com/r/blackcoin/comments/32k0u4/what_is_latest_status_of_pos_and_checkpoints_topic/
"the purpose of broadcast checkpoint is to defend against double spending when the proof-of-stake security is still not strong enough, or when certain bugs enables such attacks"
April 27, 2015, 11:24:57 AM
Will there be cake and punch? or Orange juice!? 
How have you been, my friend?
How have you been, my friend?
Everything all right- I changed from coins into internet marketing. At JVzoo it is a little bit like on a coin exchage, but you have almost 30 days money back guarantee;-)
And you still keep on mining?
My ASIC is shot, burnt it up. I'm back to mining with gpu's, for one particular coin. Once I hit my goal, I'm probably done mining for a while until I can get a farm of gpus.
April 27, 2015, 11:23:00 AM
anybody getting this error this just started happening.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
I am guessing it has to do with OC being 1 year old, but I really don't know. I'm still staking so it's ok?? I'm really not sure. Leave your wallets online until we get a fix. I know other ppl have this message, too.
It's only minor problem right now. Checkpoints are needed for the network to agree on the blockchain, for forks. But it's time to get a dev over here.
April 27, 2015, 01:17:17 AM
Will there be cake and punch? or Orange juice!?
How have you been, my friend?
How have you been, my friend?
Everything all right- I changed from coins into internet marketing. At JVzoo it is a little bit like on a coin exchage, but you have almost 30 days money back guarantee;-)
And you still keep on mining?
April 26, 2015, 05:55:27 PM
anybody getting this error this just started happening.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.
April 26, 2015, 02:04:22 PM
Will there be cake and punch? or Orange juice!?
How have you been, my friend?
How have you been, my friend?
April 26, 2015, 01:34:59 AM
So one year later:-) Happy Birthday Orangecoin :-)
April 24, 2015, 12:17:32 AM
CF report: 224278.08316
April 14, 2015, 12:46:44 AM
In case anyone's wondering, we will be enjoying 20% PoS longer than expected - if I am correct in my code reading.
So if the blockchain height is under the yearly block count of 262800, we will be enjoying 20% for another ~65900 blocks.
Code:
const int YEARLY_BLOCKCOUNT = 262800; // 365 * 2880
int64 GetProofOfStakeReward(int64 nCoinAge, unsigned int nBits, unsigned int nTime, int nHeight)
{
int64 nRewardCoinYear;
nRewardCoinYear = MAX_MINT_PROOF_OF_STAKE;
if(nHeight < YEARLY_BLOCKCOUNT)
nRewardCoinYear = 8 * MAX_MINT_PROOF_OF_STAKE;
else if(nHeight < (2 * YEARLY_BLOCKCOUNT))
nRewardCoinYear = 4 * MAX_MINT_PROOF_OF_STAKE;
else if(nHeight < (3 * YEARLY_BLOCKCOUNT))
nRewardCoinYear = 2 * MAX_MINT_PROOF_OF_STAKE;
So if the blockchain height is under the yearly block count of 262800, we will be enjoying 20% for another ~65900 blocks.
Jump to: