Topic: [ANN][OC] Orangecoin v2.0.4 ✦ PoS ✦ Anon ✦ Masternode Whitepaper ✦ Get Juiced! - page 37. (Read 72528 times)
September 10, 2015, 08:51:25 PM
Nice to see new wallet out and updates are resolving the sync problems that was going on. I have a problem now. Updated synced. All transaction history is their for me wallet however my balance is showing 0 and on block chain info showing my balance yet wallet on PC is not showing any balance of what I meant to have. Any ideas to resolve? have tried rescan and also re index no joy shows all transaction history in transactions yet no coin in wallet.
September 10, 2015, 06:00:50 PM
2.0.1 has successfully synced from scratch. Again, this sync test was done after block 292600 had already passed.
2.0.1 FTW!!!!
2.0.1 FTW!!!!
Very nice that was fast!
I am very satisfied with our client and the path we took to get here, even with the forking. I'd rather it be done right with a few bumps along the way. We picked up some major improvements in the code, too.
September 10, 2015, 05:49:13 PM
2.0.1 has successfully synced from scratch. Again, this sync test was done after block 292600 had already passed.
2.0.1 FTW!!!!
2.0.1 FTW!!!!
Very nice that was fast!
September 10, 2015, 05:48:18 PM
2.0.1 has successfully synced from scratch. Again, this sync test was done after block 292600 had already passed.
2.0.1 FTW!!!!
2.0.1 FTW!!!!
September 10, 2015, 03:46:28 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!*
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!
Cheers!
-Raven
Still syncing that client, btw. @ 131000
fork me sideways. lol raven, you're a funny man.
Ha, Halo that's your GFs Job! But I will stick it to the MAN! Posted new twat on twitter! RT please!
RT'ed and tweeted again, myself.
Thank you Buddy!
September 10, 2015, 03:43:17 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!*
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!
Cheers!
-Raven
Still syncing that client, btw. @ 131000
fork me sideways. lol raven, you're a funny man.
Ha, Halo that's your GFs Job! But I will stick it to the MAN! Posted new twat on twitter! RT please!
RT'ed and tweeted again, myself.
September 10, 2015, 03:24:59 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!*
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!
Cheers!
-Raven
Still syncing that client, btw. @ 131000
fork me sideways. lol raven, you're a funny man.
Ha, Halo that's your GFs Job! But I will stick it to the MAN! Posted new twat on twitter! RT please!
September 10, 2015, 03:22:34 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!*
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!
Cheers!
-Raven
Still syncing that client, btw. @ 131000
fork me sideways. lol raven, you're a funny man.
September 10, 2015, 03:17:51 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
SOOPY FUND! SOOPY FUND! SOOPY FUND! *Chant Continues!*
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
SYNCING MACHINE! haha Halo, Soopy, GREAT FORKING WORK!
Cheers!
-Raven
September 10, 2015, 03:15:58 PM
PLEASE MAKE SURE EVERYONE GETS THE NEW CLIENT v2.0.1.
You can find it at our website: orangecoin.weebly.com
Thank you!
You can find it at our website: orangecoin.weebly.com
Thank you!
bump, new page.
September 10, 2015, 03:15:30 PM
By the way folks,
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
The only thing that wasn't mentioned about what else was changed in 2.0.1 was the PoS % formulas. Soopy had shown me this change around when I received the first client 2.0.1 to test ~1 week ago. I like the way he wrote it, very much. It's clear and definitive, and changing base values of things like the yearlyblockcount can no longer be an issue.
I'd say it's custom code for our client, the pos code in MINT and pre-2.0.1 OC was more for cloning and having a working schedule right off the bat without major code changes, just alterations for variables to adjust per cloned coin. Without having the base variable, then there is less "moving parts" in our code engine from an engineering point of view, less moving parts mean code is cleaner and more efficient and should last the test of time now.
This is the work of our dev that people really don't even realize unless they check the git. Hats off to soopy.
September 10, 2015, 02:57:42 PM
PLEASE MAKE SURE EVERYONE GETS THE NEW CLIENT v2.0.1.
You can find it at our website: orangecoin.weebly.com
Thank you!
You can find it at our website: orangecoin.weebly.com
Thank you!
September 10, 2015, 02:29:14 PM
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Thanks for your dedication, soopy. Let's get an OC address from you.
Community: hold off moving coins just yet. Let me sync this client first to make sure the forks are behind us.
September 10, 2015, 02:26:01 PM
Indeed, we are past the fork block, and the explorer is matching. Looks like we are good to go. I will sync a client from scratch now to make sure.
September 10, 2015, 02:23:56 PM
We are now at #292613 Everyone!
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
Hope everyone is experiencing the calm bliss of Staking.
Warm Regards,
~SoopY~
September 10, 2015, 02:17:54 PM
OH YEAH ONE BLOCK TO GO!!!!! BYE BYE 20%!!!!
GONE BABY GONE!
292601
GONE BABY GONE!
292601
September 10, 2015, 01:56:17 PM
Also any ideas on how to create a faucet for OC? That'd help spread the word and Juiciness of OC!
Edit:
What do we think?
http://cryptorials.io/how-to-make-your-own-bitcoin-faucet/
Edit:
What do we think?
http://cryptorials.io/how-to-make-your-own-bitcoin-faucet/
September 10, 2015, 01:51:58 PM
And for people who want to sync FASTER than it already is syncing! Here's a link to the 292522 Bootstrap:
https://www.dropbox.com/s/xi9l4wvzaeovqyn/bootstrap.7z?dl=0
Tested twice no hiccups!
Cheers!
-Raven
https://www.dropbox.com/s/xi9l4wvzaeovqyn/bootstrap.7z?dl=0
Tested twice no hiccups!
Cheers!
-Raven
September 10, 2015, 11:45:01 AM
So about that Soopy fund! I am all for it after this release!
September 10, 2015, 11:32:11 AM
Sent pm's to chainz and richie. Website is updated, 265k blockchain download removed, will put up a newer bootstrap when time allows. Going to go tweet, then I'm updating the OP.
Want me to make bootstrap? I can provide dropbox link if needed.
Soopy's link does contain the necessary file anyway, just rename blk0001.dat to bootstrap.dat but don't use the other files in the download, except .conf.
I understand that but an even more current chain doesn't hurt.
Jump to: