Topic: [OSC]OpenSourcecoin Mandatory Update 7/1/14 - page 29. (Read 153348 times)

thanks for the info. i will reupload the files i accidentally deleted them.

edit: seems google just switched the url of google drive files from docs.google to drive.google


they are all back up now.

The Windows QT v. 1.2 download link on the website is not working.  Is there another windows client download link?

we have stratum now:
stratum+tcp://stratum.coinex.pw:9025

coinex is cool, u have to register first
then

http://osc.mining.coinex.pw:80
worker.worker/pw

Hi Guys.

Can anyone please tell me what pool I could mine these at using bfgminer please?

The pool address and port number would be very handy too. ty.

very promising currency!
I see spikes arising

R3WT，这个骗子，偷挖30多W个NAN，伙同C网一起欺骗投资者。老子操你祖宗，你妈被人强奸，生下你这个逆子

I think I fixed the testnet.  My OSC address is 2C9X2eEBLdJx1aTpea6w6iwbP3krNT9zGj .  Bounty delivered. Thanks r3wt, glad to help.

The main error is the assert at line 2628 main.cpp:

In a previous post I provided a hard coded diff to help get the testnet working.  In this post I'll try to explain how to prep the testnet for a new genesis block.  This is a unix command line walk through.  It assumes that you have the source zip and already unpacked it.

Firstly,  make sure you are working from a fresh testnet dir.  OSC is coded for testnet2.


Next go to main.cpp and make the following changes:

Compile:

Run testnet for genesis block.  Run from source dir because we will have to edit the source and compile again anyways.  This build will fail on an assert and dump info for the genesis block into the debug.log file.

Open another terminal window and more/tail the debug.log.

and you should have some output regarding your genesis block:

Right of the bat, you can go to main.h and add your genesis block hash at line 51:

Then we can make the changes in main.cpp that hard code the block. First change line 20 from true to false:

Then set your ntime pulled from the log at line 49 of main.cpp:

and fill the values from the log into lines 2592-2594 of main.cpp:

Then you can update your merkel root at line 2626 in main.cpp:

Compile, then scrub testnet directory:

Run testnet:


You should have a happy happy current build with a working testnet net.  If you tail the debug.log, you can see the peer data and the irc joins.  You cannot mine until there are multiple nodes, and they confirm there is no blocks.  What I did was compile and run on another computer and did an addnode= in the conf.  I didn't mess with any of the irc settings, so the client will join the testnet2 irc channel still, and hopefully connect with other peers.  None of the production net code is changed, so you can compile this code for the latest legit update.

CoinEX updated

https://coinex.pw/trade/osc_btc

https://coinex.pw/mining/pools/OSC

To test the testnet,  make the changes in the code in the diffs below, then compile on a couple different nodes.  Tested on 32 and 64 bit mintbuntu. 

Don't forget to make a testnet.conf somewhere and use -conf= on the command line. You might need to addnode= in the config to reach your other testnet nodes. 

This might be kind of vague, so if you have any questions, let me know. It's late for me, long day.  I'm going to reproduce how I did the genesis block in the morning and do a write up here.

Edit: in the diff, lines pointing left are original file from latest release, and lines pointing right are the changes.

Edit Edit:  I took down my nodes, so if you roll with these changes it should start work from block 0 on the testnet.

R3wt,

Got a testnet going, let me know if you want the diffs for the files I changed, or if you want me to walk you through making the genesis block build and recompiling. 

不要找任何理由，如果你和C网赔偿我的损失，这就是你们的诚信，你以后发行的硬币会有很多人支持的，不然你就是臭名远播！

please visit http://opensourcecoin.org to get the latest client update, which fixes an issue with block rewards @ block height 400,000.

thanks!

calm down like. we need you to post your Nanotoken address in the nanotoken thread. no one decieved you, you are mad because of what happened, i would be to, but remember i'm trying to help you. I should be ignoring you by now, but i'm giving you the benefit of the doubt. i'd be mad if i invested 20 bitcoins in a coin and it died too. so go back to the nanotoken thread, post a picture of your balance, and how many coins you were supposed to have, and we will pay you the difference, ok? and don't worry, Nanotoken is fixed now. as support picks up, its possible the exchange will pick it back up and you can recoup your investment. i need you to calm down and play ball with me if you want your investment back. i would buy your nanotokens off of you just to shut you up if i had the money, but i don't so these are your options.

你这个骗子，操你全家，还在骗人吗，你妈被人操烂了。

In accordance with the the planned reward structure, there will be a required update in the next few days. though the affected block is > 6 months from now, 

line 968 of main.cpp will change from


to


This will allow the subsidy to begin dividing from 25 coins as was planned. at any rate i'm glad i caught the error before it made a problem. left as it is, the subsidy would drop to 1 @ block 400,000 crippling supply and likely unsettling miners. so thats the change. i will push the update this week probably, new client versions and the whole nine yards

I still haven't heard from x3maniac, is anyone able to help me with OSC and stratum? I posted on the previous page about stratum failing to submit blocks to the wallet.

well after keeping a watchful eye on the network i've came to the conclusion there may not need to be an update yet. for now i'm playing it by ear and trying to judge how it reacts to large fluctuations in hashrate. the jump from 80 ghs to 380 ghs produced only a 2000 point spike in difficulty, where as previously it was resulting in large 20000 point swing from 140 gh/s to 1 th/s. the real test will come next time an above average spike in hashrate comes, like we saw with the 3 th/s spike on the 17th that virtually froze the network for a few hours, with difficulty close to 300,000.

that's my little update for sunday evening, i will let you know if and when something changes with the network. it seems to be stable for now. Also the launch of security testing on coinbit begins tommorow, and launch could be as early as friday. thanks, and have a good sunday evening my crypto friends.

r3wt

planned update for tomorrow. more details to follow later this evening.

there seems to be a flaw in the difficulty retargeting every block, and there seems to be a large asic jumping on and off of the network which is causing difficulty stranding and long block times. i'm having a look into how it can be fixed.