[ANN] official NovaCoin thread - the original PoS+scrypt coin.

[Balthazar]

Code:

{
    "account" : "",
    "category" : "immature",
    "amount" : 100.40000000,
    "confirmations" : 404,
    "blockhash" : "f5b9490fa77577381569418f7522f1076111c5004892b00a38ba68bb31664daf",
    "blockindex" : 1,
    "txid" : "dff392162e709bd6070ba397cedc0e60a75cb7ce80f5919155e182b13d1587e3",
    "time" : 1363643971
},

Suddenly found the PoS block.   Didn't thought that I have old INPUTs in the wallet, because done a lot of transactions in this month during the testing of p2pool fixes.

[hanzac]

Code:

{
    "account" : "",
    "category" : "immature",
    "amount" : 100.40000000,
    "confirmations" : 404,
    "blockhash" : "f5b9490fa77577381569418f7522f1076111c5004892b00a38ba68bb31664daf",
    "blockindex" : 1,
    "txid" : "dff392162e709bd6070ba397cedc0e60a75cb7ce80f5919155e182b13d1587e3",
    "time" : 1363643971
},

Suddenly found the PoS block.   Didn't thought that I have old INPUTs in the wallet, because done a lot of transactions in this month during the testing of p2pool fixes.

You're so lucky. Wow, I'd say it's a big number!

[Balthazar]

Actually reward is 0.4 coins.

http://novacoin.ru/block/f5b9490fa77577381569418f7522f1076111c5004892b00a38ba68bb31664daf

But the 100 would have been nicer, of course.

[ryhel]

I compared

forrestv - https://github.com/forrestv/p2pool/blob/master/p2pool/main.py
Balthazar - https://github.com/CryptoManiac/p2pool/blob/master/p2pool/main.py

I don't see

Code:

   parser.add_argument('-a', '--address',
        help='generate payouts to this address (default: <address requested from bitcoind>)',
        type=str, action='store', default=None, dest='address')

Why we can't set external novacoin address as default payout address?
Why you disabled this nice feature?

[Balthazar]

It was removed due to NovaCoin's protocol limitations. For each block the NVC network requires digital signature from the owner of one of the destinations in coinbase transaction. Thus, the generation is possible only with addresses that belongs to miner. You are able to specify custom public key by editing cached_payout_pubkey file, but it's not recommended. It's risky due to possibility of invalid blocks generation.

[Balthazar]

v0.3.3 released. This release fixes entropy bit calculation problem, which was discovered yesterday.

Sources: https://github.com/CryptoManiac/novacoin/
Binary builds: https://sourceforge.net/projects/novacoin/files/

You need to update your nodes as soon as possible, otherwise you risk to be affected by blockchain fork which will happen soon (deadline is approximately ~30.03.2013) for unfixed clients.

P.S. Thanks to SunnyKing for help with investigating this issue.  

[Sunny King]

v0.3.3 released. This release fixes entropy bit calculation problem, which was discovered yesterday.

Sources: https://github.com/CryptoManiac/novacoin/
Binary builds: https://sourceforge.net/projects/novacoin/files/

You need to update your nodes as soon as possible, otherwise you risk to be affected by blockchain fork which will happen soon (deadline is approximately ~30.03.2013) for unfixed clients.

P.S. Thanks to SunnyKing for help with investigating this issue.  

You are welcome Balthazar.

Please note block chain re-download is required for this upgrade to function properly.

ppcoin is not affected by this issue which is introduced by p2pool support for novacoin.

[Balthazar]

I changed blkindex format, so users are forced to re-download blockchain before new client will be able to function.

P.S. Sent alert, it will affect 60002 and 60003.

[hanzac]

Balthazar, I can't connect to p2p peers anymore, is there any changes to the network?

[Balthazar]

Balthazar, I can't connect to p2p peers anymore, is there any changes to the network?

By the p2p you mean p2pool? If that guess is correct I can answer "no". Because the last commit into p2pool tree was 8 days ago.

P.S. tried to start p2pool with 0.3.3, it works fine. 

[hanzac]

Balthazar, I can't connect to p2p peers anymore, is there any changes to the network?

By the p2p you mean p2pool? If that guess is correct I can answer "no". Because the last commit into p2pool tree was 8 days ago.

P.S. tried to start p2pool with 0.3.3, it works fine.  

P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming)
Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:

I don't know what's wrong with it, the startup is fine with no errors but there're no peers are connectable?

BTW, I also notice that the p2pool running behind the route always has 0 incoming connections, does the upnp work?

[Balthazar]

Balthazar, I can't connect to p2p peers anymore, is there any changes to the network?

By the p2p you mean p2pool? If that guess is correct I can answer "no". Because the last commit into p2pool tree was 8 days ago.

P.S. tried to start p2pool with 0.3.3, it works fine.  

P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming)
Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:

I don't know what's wrong with it, the startup is fine with no errors but there're no peers are connectable?

Are the 9777 & 6667 ports accessible for outcoming connections? That's required for p2pool.

My case (I'm behind the NAT):

2013-03-27 03:53:33.839000 P2Pool: 5769 shares in chain (2923 verified/5769 total) Peers: 6 (0 incoming)

// I'll back few hours later.

[hanzac]

Balthazar, I can't connect to p2p peers anymore, is there any changes to the network?

By the p2p you mean p2pool? If that guess is correct I can answer "no". Because the last commit into p2pool tree was 8 days ago.

P.S. tried to start p2pool with 0.3.3, it works fine.  

P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming)
Local: 0H/s in last 0.0 seconds Local dead on arrival: Expected time to share:

I don't know what's wrong with it, the startup is fine with no errors but there're no peers are connectable?

Are the 9777 & 6667 ports accessible for outcoming connections? That's required for p2pool.

My case (I'm behind the NAT):

2013-03-27 03:53:33.839000 P2Pool: 5769 shares in chain (2923 verified/5769 total) Peers: 6 (0 incoming)

I think yes, I've used following cmd to turn off iptables:
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT

it works last week, this week I found I can't connect to external peers.

The following ports are opened, after I run p2pool:

Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:8344          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:7777            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:8336            0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:9777            0.0.0.0:*               LISTEN
tcp6       0      0 :::22                   :::*                    LISTEN
tcp6       0      0 :::111                  :::*                    LISTEN
udp        0      0 0.0.0.0:43218           0.0.0.0:*
udp        0      0 0.0.0.0:111             0.0.0.0:*
udp        0      0 0.0.0.0:750             0.0.0.0:*
udp        0      0 0.0.0.0:5353            0.0.0.0:*
udp6       0      0 :::111                  :::*
udp6       0      0 :::750                  :::*

It seems that there's no 6667 port, how it is opened?

[meebs]

Is it possible to generate stake while having the wallet encrypted? (using QT client) I found that with PPC I was never able to do so as it said stake couldn't be generated due to a locked wallet...

[maunderingcabal]

I have the latest version of the wallet and it says warning checkpoint too old. wait for block to download, or notify dev.... and it's doing nothing. What am I doing wrong?

[hanzac]

I have the latest version of the wallet and it says warning checkpoint too old. wait for block to download, or notify dev.... and it's doing nothing. What am I doing wrong?

I think check point old is not a big issue, I also have this warning but it works fine.

[Balthazar]

I have the latest version of the wallet and it says warning checkpoint too old. wait for block to download, or notify dev.... and it's doing nothing. What am I doing wrong?

It's just information message, you can ignore it. Anyway, it should disappear now.

[maunderingcabal]

I sent 1 nvc to that address as a test and it didn't show up. any ideas? Warning is still up?

[Balthazar]

Is it possible to generate stake while having the wallet encrypted? (using QT client) I found that with PPC I was never able to do so as it said stake couldn't be generated due to a locked wallet...

Stake generation is impossible while your wallet is locked.

[maunderingcabal]

I just deleted the block file and I'm trying to download again. Maybe My payment will show up then?