Sounds you took an old wallet, from a previous NoirShares version, stuck it in the same folder, and tried to open it with the new NoirShares daemon.

Not sure that is going to work.

What happens if you just open it with no wallet (let it create one), and use the importprivkey command to import your keys?

I think one lucky person found a 2222 block (rare)

Use a regular cpu like the rest of us.  Let's not get greedy.

Most probably because your shares2.txt and shares.txt aren't in the current folder you're starting the Noirsharesd from.

That's your problem.  By the time you mine a block, it will be stale. You need >5 nodes.

Please don't ask me for a node list. I've copy/pasted a bunch of addnode= list within the last 12 hours. Please read my previous posts to find it.

A couple, yes.

If you NoirSharesd getinfo, does it say:

    "version" : "v0.2.3.1-beta",
    "protocolversion" : 60010,

How many connections do you have?  "connections" :

If you run this:

NoirSharesd getmininginfo

Do you see this?

"generate" : true,

Ok, so as long as we don't transfer coins, we're good for the time being.

So heads up people. If you earn coins, don't use the sendtoaddress command until Barwizi is done.

By the way, I've been watching my node (and other nodes) interacting and syncing. This looks pretty good so far..

A stable 2.0 chain (and Linux/Windows clients) are most important at this point. Thanks for discovering it.

Please starve off any new features until we have that at least.

Try this....  (gen=1 means try to generate new PoW coins)


server=1
gen=1
daemon=1
listen=1
rpcuser=YOURUSERNAME
rpcpassword=YOURPASSWORD
maxconnections=35
addnode=70.54.66.159
addnode=189.181.201.75
addnode=207.245.41.195
addnode=184.68.133.150
addnode=192.64.5.200
addnode=107.170.52.105
addnode=41.78.78.2
addnode=54.186.239.68
addnode=91.134.53.161
addnode=192.64.4.13
addnode=24.67.29.246
addnode=207.245.41.195
addnode=107.170.52.105
addnode=68.54.118.59
addnode=75.83.196.109
addnode=14.20.5.117
addnode=130.204.172.168
addnode=89.151.189.195

(I'm temporarily back by the way, giving this another chance)

The chain was reset to 0 blocks, so any new PoW mined coins from the previous alpha release are lost.

The snapshot coins are still ready to be claimed by importing your private key if you want to do that. (I'm waiting for a couple of weeks before I do that just in case)

The best thing to do is open up a new wallet, and PoW cpu mine if you want to run a node on the network and help secure it.

So strange. One Windows Machine I uploaded an earlier Noirshares wallet which got malware an hour later. (just sayin')

The Linux machine I've been compiling source, likes to connect to Barwizi's VPS node 8.38.76.74 but it always claims there is only 81 blocks in the chain. So the VPS seed node is giving different answers (I was previously synced to it on another box, and we were at 1700 blocks. Now it is sending out that 81 blocks is the current height to a new client.  It's almost configured to stop extra nodes coming on the net)

There's another longer chain out there +2000 blocks, but the blocks were created without paying a mandatory fee, and 0.2.2.2 complains about it, so it won't reorg based on the longer chain either.

This really starts to smell of a manipulated pre-mine by buggy code.

I've had enough.

Good luck to all of you.  Oh, and notice I didn't have any big red scam warnings.  That would be childish.

I'm outta here.

If you are using Linux

make sure you have gen=1 in your NoirShares.conf file. It defaults to gen=0 (mining off)

I'm having problems syncing again though. I see plenty of this in my debug.log

InvalidChainFound: invalid block=00af670a27e730bd4e91  height=1075  trust=40886  date=09/21/14 05:54:46
InvalidChainFound:  current best=00a216b4c994cc0d50b8  height=81  trust=411  date=09/18/14 16:05:30
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

This basically means the Linux client is broken. It can't follow the longest chain.  The alpha code isn't working properly.

Yes, it is a bug confirmed by other person.  This alpha code needs to have that fixed.

Suggestion to all:

If you donate your money to a GF, or to participate in mining operations, I highly recommend you investigate what type of reporting and transparency will take place before doing so..  (very few of you did that as I remember).

I remember seeing all the posts that send "Here's another 0.25 btc 1dasdjkdfajdsakldasfljdskl"

I shook my head at how easily people donated their money this way, just blindly throwing it into a pot on some google spreadsheet and some written up documents.

My feelings toward Barwizi is that he's a decent developer software wise, but not quite as good at running companies.  I think any mishaps are attributed more to lack of communication and understanding by everyone involved.

I hope if we can get through this, and get NRS 2.0 at exchanges, and a decent client, we can all learn from this and proceed on a better premise.  GF holders may feel that beating this issue into a public spectacle for personal satisfaction is a good idea. However, what they are also doing, is creating the potential for snapshot NRS holders to lose out as well.   Let's not sink the entire ship here.  What we need is a win-win situation.

There is a way to amicably get this resolved.

Oh, and please let's not re-quote pages and pages of screens in each post. The scroll wheel on my mouse is near broken.

Also, it is long understood that investing in mining rigs of any sort usually results in a loss over time.  It may have worked in the early days of Bitcoin, but not any longer.   At best, you can break even on your investment.  Mining is more of a hobby, or a game of chance. That's it.  A very bad investment for long term gain.

With that being said, continue to quibble over your 3-10 BTC while we drag NRS and Barwizi through the mud. All I see here is more future carnage happening with our snapshot shares, and I don't like it.

Since GF investors are seemingly paving the way for my snapshot NRS to go down with them, I feel I have a right to state my concerns about it.

It would be my recommendation as a bystander that you don't mint with your wallet during the Alpha code phase.

Instead, if you want to participate in mining new coins (and minting them), you do it will an empty wallet, that has no passphrase and is not locked.

I own NRS in the snapshot myself, and I haven't imported my keys until the code is at least beta and more stable.

Right now I have new wallet (with no passphrase) that has less than 10 newly mined NRS in it, and that's what I'm using for the time being.

My client is synced at block 1707 so far. Since there is no block explorer, I'm assuming this is the correct chain?

I'm getting some 2.2222 but when when I was on a bad chain fork before, I did see 22.2222 a couple times.

Question:

Shouldn't alpha code be running on testnet while it is being developed.

We should have a simple beta chain going with no new features, so the chain still exists and people can start trading NRS 2.0 and mining it.

I'm having a hard time running Noirbits-master and not getting stuck at block 119, or finding alternative nodes.  IRC doesn't seem to be giving out nodes (or there are simply hardly any running).

It is my guess there are multiple forked chains running right now.  We also need a block explorer.

To give an example, when Sunny King runs alpha, it is always on testnet.  He doesn't bring it onto a live chain until it's beta.

In Windows, you have to create a text file named "NoirShares.conf" and put it into
C:\Users\YOURUsername\AppData\Roaming\NoirShares

The conf file (if you want to mine coins with your CPU) will be something like this:

(Before you add this file, close down any open Noirshares 2.0 wallet, put the file, and then restart the Noirshares 2.0 wallet again)

NoirShares.conf file will contain this:

server=1
gen=1
daemon=1
listen=1
rpcuser=YOURUSERNAME
rpcpassword=YOURPASSWORD
maxconnections=35
addnode=8.38.76.74
addnode=70.54.66.159
addnode=189.181.201.75
addnode=207.245.41.195
addnode=184.68.133.150
addnode=192.64.5.200
addnode=107.170.52.105
addnode=41.78.78.2
addnode=54.186.239.68
addnode=91.134.53.161
addnode=192.64.4.13
addnode=24.67.29.246
addnode=207.245.41.195
addnode=107.170.52.105
addnode=68.54.118.59:
addnode=75.83.196.109
addnode=14.20.5.117
addnode=130.204.172.168
addnode=89.151.189.195

Alternatively, if you are using Linux, this file will be in /home/YOURUSERNAME/.NoirShares/NoirShares.conf

We are at block 380 already, with a really easy difficulty. Mining blocks should happen easily.  The longest chain wins, so make sure you get this NoirShares.conf file ready, and join the chain and start mining coins.

It is Alpha code, so there is no guarantee that the coins you mine will be real, but until Barwizi addresses this further, you might as well run the wallet with gen=1 so you are mining coins with your CPU on the longest chain (which is happening right now).