[OSC]OpenSourcecoin Mandatory Update 7/1/14

[sacskate]

GET ON COINEX AND START TRADING... LETS GET SOME VOLUME GOING

[sunsofdust]

I just saw that OSC is also on coinwarz.  Sweet!

[r3wt]

Avast reports as malware.

pics? report? i have avast I.S. on my windows machine and not a peep. possible that you are fudding, as its highly unlikely someone was able to inject it on google drive, however i'll reserve to comment on it until you provide proof of your accusation.

\
edit: downloaded from google drive and not a peep from avast or malware bytes pro. i'll unpack it with isa pro and scan each object for good measure. no one falsely accuses me of packing malware and gets away with it 

[iram3130]

Not in cryptsy yet? Anyone experiencing anti virus popping up?

[r3wt]

Avast reports as malware.

pics? report? i have avast I.S. on my windows machine and not a peep. possible that you are fudding, as its highly unlikely someone was able to inject it on google drive, however i'll reserve to comment on it until you provide proof of your accusation.

\
edit: downloaded from google drive and not a peep from avast or malware bytes pro. i'll unpack it with isa pro and scan each object for good measure. no one falsely accuses me of packing malware and gets away with it  

I'm not accusing you of anything, simply stating what happened. I don't have a screenshot as I panicked and killed my internet connection and am now in the process of format/reinstall but I do have this screenshot from where Avast sandboxed it.

yeah avast automatically puts new exe's into the sandbox..... thanks for the bad pr though...

[r3wt]

Avast reports as malware.

pics? report? i have avast I.S. on my windows machine and not a peep. possible that you are fudding, as its highly unlikely someone was able to inject it on google drive, however i'll reserve to comment on it until you provide proof of your accusation.

\
edit: downloaded from google drive and not a peep from avast or malware bytes pro. i'll unpack it with isa pro and scan each object for good measure. no one falsely accuses me of packing malware and gets away with it  

I'm not accusing you of anything, simply stating what happened. I don't have a screenshot as I panicked and killed my internet connection and am now in the process of format/reinstall but I do have this screenshot from where Avast sandboxed it.

yeah avast automatically puts new exe's into the sandbox..... thanks for the bad pr though...

That has never occurred for me whether bitcoin-qt, litecoin-qt or non bitcoin related programs, this is a first.

thats because bitcoin and litecoin are digitally signed with gitian builder. i lack the hardware required to build a program with gitian builder, hence the unsigned binaries. eventually i will upgrade my build machine to a modern motherboard with a bios that supports hardware virtualization. all this being said, its fairly common knowledge that new unsigned binaries(or to be more specific, new coin clients) are some times marked as suspicious by antivirus programs(specifically Avast and Microsoft smartscreen, i have both and they often fight over who gets to block the application first. in fact, everytime i build a new client, windows 8 "smart screen" blocks me from opening it immediately after i click on it. like i said, calm your tits lol.

ps: if you're this concerned with security, you may consider launching all altcoin clients in their own separate virtual machine. this is more or less what avast sandbox does when it finds something it deems suspicious.

[Tommo_Aus]

Tried mining at my pool, looks to be a problem with submitting blocks. I've seen this problem on 2 other coins, ADT and something else, they were both scrypt coins. First time I've come across it with a sha256 coin. Here are the stratum logs:

Code:

2013-10-16 21:37:58,635 INFO template_registry # We found a block candidate! 00000000000128ef2851a4650ec796dfa1ba5d0d6758aa5d
675236e6627a39e0
2013-10-16 21:37:58,639 INFO interfaces # 00000000000128ef2851a4650ec796dfa1ba5d0d6758aa5d675236e6627a39e0 (56500) valid Tomm
o.3
2013-10-16 21:37:58,646 INFO template_registry # New template for 00000000002003267f3d2eb04ada518e608adcdd811b48325b9ace4d4cf
fe4f8
2013-10-16 21:37:58,647 INFO subscription # BROADCASTED to 3 connections in 0.000 sec
2013-10-16 21:37:58,648 INFO template_registry # Update finished, 0.002 sec, 1 txes
2013-10-16 21:37:58,651 ERROR bitcoin_rpc # Problem Submitting block 500 Internal Server Error
Traceback (most recent call last):
  File "/mystratumlocation/stratum-mining-litecoin/lib/bitcoin_rpc.py", line 49, in submitblock
    resp = (yield self._call('getblocktemplate', [{'mode': 'submit', 'data': block_hex}]))
Error: 500 Internal Server Error

And the stratum code:

Code:

def submitblock(self, block_hex, block_hash_hex):
        # Try submitblock if that fails, go to getblocktemplate
        try:
            resp = (yield self._call('submitblock', [block_hex,]))
        except Exception:
            try:
--line 49--  resp = (yield self._call('getblocktemplate', [{'mode': 'submit', 'data': block_hex}]))
            except Exception as e:
                log.exception("Problem Submitting block %s" % str(e))
                raise

        if json.loads(resp)['result'] == None:
            # make sure the block was created.
            defer.returnValue((yield self.blockexists(block_hash_hex)))
        else:
            defer.returnValue(False)

Is there anything different to submitblock with OSC compared to the usual sha256 coins? I have many other sha256 coins on my pool and they don't have this problem. I never figured out what the issue was with the other coins so had to take them off the pool, any help would be excellent so I can get it mining.

[r3wt]

Tried mining at my pool, looks to be a problem with submitting blocks. I've seen this problem on 2 other coins, ADT and something else, they were both scrypt coins. First time I've come across it with a sha256 coin. Here are the stratum logs:

Code:

2013-10-16 21:37:58,635 INFO template_registry # We found a block candidate! 00000000000128ef2851a4650ec796dfa1ba5d0d6758aa5d
675236e6627a39e0
2013-10-16 21:37:58,639 INFO interfaces # 00000000000128ef2851a4650ec796dfa1ba5d0d6758aa5d675236e6627a39e0 (56500) valid Tomm
o.3
2013-10-16 21:37:58,646 INFO template_registry # New template for 00000000002003267f3d2eb04ada518e608adcdd811b48325b9ace4d4cf
fe4f8
2013-10-16 21:37:58,647 INFO subscription # BROADCASTED to 3 connections in 0.000 sec
2013-10-16 21:37:58,648 INFO template_registry # Update finished, 0.002 sec, 1 txes
2013-10-16 21:37:58,651 ERROR bitcoin_rpc # Problem Submitting block 500 Internal Server Error
Traceback (most recent call last):
  File "/mystratumlocation/stratum-mining-litecoin/lib/bitcoin_rpc.py", line 49, in submitblock
    resp = (yield self._call('getblocktemplate', [{'mode': 'submit', 'data': block_hex}]))
Error: 500 Internal Server Error

And the stratum code:

Code:

def submitblock(self, block_hex, block_hash_hex):
        # Try submitblock if that fails, go to getblocktemplate
        try:
            resp = (yield self._call('submitblock', [block_hex,]))
        except Exception:
            try:
--line 49--  resp = (yield self._call('getblocktemplate', [{'mode': 'submit', 'data': block_hex}]))
            except Exception as e:
                log.exception("Problem Submitting block %s" % str(e))
                raise

        if json.loads(resp)['result'] == None:
            # make sure the block was created.
            defer.returnValue((yield self.blockexists(block_hash_hex)))
        else:
            defer.returnValue(False)

Is there anything different to submitblock with OSC compared to the usual sha256 coins? I have many other sha256 coins on my pool and they don't have this problem. I never figured out what the issue was with the other coins so had to take them off the pool, any help would be excellent so I can get it mining.

you will have to either switch to pushpool or edit the blocktemplate to include the transaction message field. a good place to start is serialize.h if you need help, contact x3maniac

[Tommo_Aus]

What's the transaction message field? Is it something that goes into the submitblock hex?

[r3wt]

What's the transaction message field? Is it something that goes into the submitblock hex?

yes

[Tommo_Aus]

Hrm I think this might be a bit out of my league, I've got a couple of moopless stratum threads I'm looking through so hopefully I find an answer there.

[r3wt]

Hrm I think this might be a bit out of my league, I've got a couple of moopless stratum threads I'm looking through so hopefully I find an answer there.

you need to contact x3 maniac, the operator of dsync pulls. he faced the issue you were facing and rewrote some parts of his stratum miner for OSC.

[Tommo_Aus]

Right o sent him a message, hopefully he has some good words to say

[r3wt]

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.

[r3wt]

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

[r3wt]

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

[Tommo_Aus]

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.

[r3wt]

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

Code:

else if (nHeight > 256000 && nHeight < 400000) {nSubsidy = 25 * COIN;}                 // 25 coins

to

Code:

else if (nHeight > 256000) {nSubsidy = 25 * COIN;}                 // 25 coins

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

[like]

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

[r3wt]

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

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.