Pages:
Author

Topic: Nucleon | PoW Masternodes (x11 Mining) | Masternode Hosting | INTERNAL SENTINEL - page 2. (Read 460730 times)

member
Activity: 497
Merit: 24
We've got a NEON tipbot added to http://discord.nucleon.cc now and will be doing rains quite often in the #no-rules channel - More rain is coming in a minute.. JOIN QUICK!

Hey swapsie,

Have ya thought about using neon as a gaming tip coin ontop of its other uses it already has?
could get some mainstream investors onto it and get some cheap advertisement threw streamer/twitch channels..
Pm me if ya want to talk about it more in dept.

Da JA
Stabycroc ;_)>

We are open to any and pretty much all suggestions for promoting NEON at this time. Currently, several members of our team are trying to finish up v2.3 as soon as possible, so our time for marketing has been minimal so far; getting close, though!
This is like some kind of reunion ?

Like the union u will have with fed police/cyber crime unit soon dw...
i gave u months to fix me up and do what is right buy some 1 that always done right by u but nah, looks like im going to have to go to police about ur actions ACP.

Swapsie might of had a USA Ego in the early days but he never stole from me.
At least swapsie learnt from past and making good for the future..

U ACP should go join the crown dev crew u would fit in well with there get carried in crypto promo of there coin in clean way then premine the f out of mineable coin for there own self greed and not give a F about promoters/investors that been with them since there start and help make them become top coins to just kill the good that others put into them for "superblocks" and self greed.
but still dont know the difference from POs to mnpos and other basic crypto wording.
Basically how to kill a coin others built the backbone of for years, u should know this better than most respect in crypto isnt bought its ernt...

My word is crypto angel gold, u and the crown devs words isnt worth 1c...people might not like me for telling crypto truths but they trust my word.
I told u to pm to sort ur theft out but just come here to talk shit this is wat u get....
even when the price of the coin u stole is worth 1/10 of wat it was when u stole it, u still dont try return it..u made profit of the stolen coins but still even at the 1/10 of the price u got paid out for u dont return the coins.

Da ja
Stabycroc ;_)>
ACP
hero member
Activity: 612
Merit: 520
We've got a NEON tipbot added to http://discord.nucleon.cc now and will be doing rains quite often in the #no-rules channel - More rain is coming in a minute.. JOIN QUICK!

Hey swapsie,

Have ya thought about using neon as a gaming tip coin ontop of its other uses it already has?
could get some mainstream investors onto it and get some cheap advertisement threw streamer/twitch channels..
Pm me if ya want to talk about it more in dept.

Da JA
Stabycroc ;_)>

We are open to any and pretty much all suggestions for promoting NEON at this time. Currently, several members of our team are trying to finish up v2.3 as soon as possible, so our time for marketing has been minimal so far; getting close, though!
This is like some kind of reunion ?
newbie
Activity: 25
Merit: 0
What do the works on the new wallet look like?
When version 2.3 will be available?
sr. member
Activity: 664
Merit: 250
newbie
Activity: 199
Merit: 0
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,

https://github.com/MealwormsBiz/Nucleon/releases/tag/v2.2.0    QT Windows? PAge not FOUND. any idea. is NEON coin dead or what? the other day I got a certain amount of coins, they never came to my wallet

  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
Any chance you can try a different device and if it works send device details of computer with issue so we can debug after our update is done?

debian 9 64bits

making progress...now stuck at block 11754

bootstrap files?
github project up to date?
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
Any chance you can try a different device and if it works send device details of computer with issue so we can debug after our update is done?

debian 9 64bits

making progress...now stuck at block 11754

bootstrap files?
github project up to date?
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
Any chance you can try a different device and if it works send device details of computer with issue so we can debug after our update is done?

debian 9 64bits

making progress...now stuck at block 11754
newbie
Activity: 4
Merit: 0
Saw at discord that you're making some progress with v2.3.
After that, what's next? I mean, any new promotion for Neon?
I think that knowing some of what's coming could attract some new investors.
newbie
Activity: 5
Merit: 0
Hi there, (sorry for my English I'm French ^^)

For MN, I need to sending My Nucleon Coinexchange => Nodemasters.net ? where is my key generating?

Thanks...
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
Any chance you can try a different device and if it works send device details of computer with issue so we can debug after our update is done?

debian 9 64bits
member
Activity: 210
Merit: 20
https://onlydoge.fans/
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
Any chance you can try a different device and if it works send device details of computer with issue so we can debug after our update is done?
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
I'm going to do a 100000+ NEON rain in about 10 minutes in http://discord.nucleon.cc
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?

Qt is just a daemon with a face you can click
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon

Is there any chance you can try to sync a daemon?
newbie
Activity: 5
Merit: 0
This looks fantastic!!  Nice update glad to see you're on more exchanges too!!  Obviously a good sign things are getting bigger?
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io







MCT.Plus
Wadax.io
CoinExchange
Rocket-Exchange








NEON/BTC Market
http://btc.nucleon.cc

NEON/ETH Market
http://eth.nucleon.cc

NEON/ENY Market
http://eny.nucleon.cc

NEON Wallet Downloads
http://wallets.nucleon.cc

NEON Source Code
http://github.nucleon.cc

NEON Discord Server
http://discord.nucleon.cc

NEON Bitcointalk Thread
http://bitcointalk.nucleon.cc

NEON on Twitter
http://twitter.nucleon.cc

NEON on YouTube
http://youtube.nucleon.cc

NEON Block Explorer
http://explorer.nucleon.cc

NEON Mining Statistics
http://miningstats.nucleon.cc

NEON Masternode Statistics
http://masternodestats.nucleon.cc

NEON Shared Masternode Hosting
http://hosting.nucleon.cc







                   



























                   










Developer Note: You will not be required to use third-party software such as Python and/or Sentinel, to run a Nucleon Masternode. Nucleon is the first coin to feature Internal Sentinel, which is hardcoded into the wallet and automatically run and will be fully configured for you.. inside the wallet!







  • 8 minute block time with 2MB blocks
  • X11 Mining Algorithm (CPU/GPU/ASIC)
  • Instant transactions using InstantSend
  • Decentralized second-tier masternode network
  • Superior transaction anonymity using PrivateSend
  • Dark Gravity Wave difficulty adjustment algorithm
  • NEON now uses VRX/Velocity difficulty retargeting
  • NEON is the first to implement the DNA Retargeting System







In addition to traditional Proof of Work (PoW) rewards for mining Nucleon, users are also rewarded for running and maintaining special servers called masternodes. Thanks to this innovative two tier network, Nucleon can offer innovative features in a trustless and decentralized way. Masternodes are used to power PrivateSend, InstantSend, and the governance and treasury system. Users are rewarded for running masternodes: 90% of the block reward is allocated to pay the masternode network. Masternodes are resposible for processing both PrivateSend and InstantSend. Masternode owners must have possession of 100,000,000 Nucleon, which they prove by signing a message and broadcasting to the network. Those coins can be moved at any time, but moving them will cause the masternode to fall out of queue and stop earning rewards. Masternode users are also given voting rights on proposals. Each masternode has one vote and this vote can be used on budget proposals or important decisions that affect Nucleon. Masternodes cost money and effort to host so they are paid a percentage of the block reward as an incentive, which is 90% of the Block Reward







PrivateSend gives you true financial privacy by obscuring the origins of your funds. All the Nucleon in your wallet is comprised of different inputs, which you can think of as separate, discrete coins. PrivateSend uses an innovative process to mix your inputs with the inputs of two other people, without having your coins ever leave your wallet. You retain control of your money at all times





        

  • PrivateSend begins by breaking your transaction inputs down into standard denominations. These denominations are 0.01 NEON, 0.1 NEON, 1 NEON and 10 NEON – much like the paper money you use every day
    Your wallet then sends requests to specially configured software nodes on the network, called “masternodes”. These masternodes are informed then that you are interested in mixing a certain denomination. No identifiable information is sent to the masternodes, so they never know “who” you are
    When two other people send similar messages, indicating that they wish to mix the same denomination, a mixing session begins. The masternode mixes up the inputs and instructs all three users’ wallets to pay the now-transformed input back to themselves. Your wallet pays that denomination directly to itself, but in a different address (called a change address)
    In order to fully obscure your funds, your wallet must repeat this process a number of times with each denomination. Each time the process is completed, it’s called a “round”. Each round of PrivateSend makes it exponentially more difficult to determine where your funds originated. The user may choose between 2-8 rounds of mixing
    This mixing process happens in the background without any intervention on your part. When you wish to make a transaction, your funds will already be anonymized. No additional waiting is required
    Note that PrivateSend transactions will be rounded up so that all transaction inputs are spent. Any excess Nucleon will be spent on the transaction fee

    IMPORTANT: Your wallet only contains 1000 of these “change addresses”. Every time a mixing event happens, one of your addresses is used up. Once enough of them are used, your wallet must create more addresses. It can only do this, however, if you have automatic backups enabled. Consequently, users who have backups disabled will also have PrivateSend disabled







By using a two-tier network, Nucleon is able to quickly confirm transactions much faster than most other networks. Traditional decentralized cryptocurrencies must wait for certain period of time for enough blocks to pass to ensure that a transaction is both irreversible and not an attempt to double-spend money which has already been spent elsewhere. This process is time-consuming, and may take anywhere from 15 minutes to one hour for the widely accepted number of six blocks to accumulate. Other cryptocurrencies achieve faster transaction confirmation time by centralizing authority on the network to various degrees. Nucleon suffers from neither of these limitations thanks to its second layer network of masternodes. Masternodes can be called upon to form voting quorums to check whether or not a submitted transaction is valid. If it is valid, the masternodes “lock” the inputs for the transaction and broadcast this information to the network, effectively promising that the transaction will be included in subsequently mined blocks and not allowing any other spending of these inputs during the confirmation time period. InstantSend technology will allow for cryptocurrencies such as Nucleon to compete with nearly instantaneous transaction systems such as credit cards for point-of-sale situations while not relying on a centralized authority. Widespread vendor acceptance of Nucleon and InstantSend could revolutionize cryptocurrency by shortening the delay in confirmation of transactions from as long as an hour (with Bitcoin) to as little as a few secondsBy using InstantSend, Nucleon is able to compete with other, more mainstream technologies such as credit card and PayPal payments without using a central authority, thus keeping the reality of decentralized financial security a reality







Nucleon has a unique Block Reward Structure that has never been seen before. Not only will it slowly trend downwards to ensure inflation does not get out of control, but it will also feature larger blocks on the way down to provide miners an incentive to keep their mining rigs on the network. By using the x11 mining algorith, Nucleon welcomes the use of ASIC mining to ensure long-term network security on the blockchain. By encouraging ASIC mining, Nucleon hopes to entice users to keep their rigs on our network with interesting block rewards that will reward everyone involved from users to miner to Masternode hosts. The general trend for Nucleon blocks will lower rewards by 1 NEON per block, but it is not a straight line down. The formula used will create blocks with a bump of significantly larger rewards on the way down ensuring longetivity with interesting rewards, while also controlling inflation by focusing on a consistently downward trend

As a long-term solution to retaining miners, Nucleon will never have a reward that generates less than 1000 NEON per block; there is a hard-coded failsafe that ensures 1000 coins is the lowest possible reward for any block, no matter what!







The Nucleon Development Team is comprised of some of the most experienced developers who have been involved with cryptocurrency and related services for many years. Not only are we all extremely versed in this space, we have also worked behind the scenes for many of your favorite coins and sites! The team is a collaboration of five people who have been writing, editing, and forking code such as coins, mining pools, online and offline graphics such as wallet designs, websites, and logos, services like web wallets, block explorers, payment processors, and tons more; if crypto has it, one of us has done it! All of this experience and collective learning has lead us to each other for Nucleon and we are all very excited to continue working on a dedicated project together. Nucleon development is lead by iGotSpots and Nashanas. Web services like mining pools, block explorers, and masternode sharing programs are run by g420 and pjcltd. Wallet layout has been designed by Zoras. While it sounds weird to use psuedonyms as your faithful team, most of us are not anonymous at all and are very easy to identify. We are here to service the Nucleon community and our goals are exactly the same: provide the best product and the best user experience possible to each and every single user. Whether you hold 1 NEON or 120 millon NEON, you are our main focus. We look forward to interacting with the community and taking every suggestion into consideration to better improve the experience and returns for you, the individual user







stratum+tcp://bigmine.org:3944 -u NEON_ADDRESS -p c=NEON

stratum+tcp://bpool.online:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://miner2pool.ovh:3533 -u NEON_ADRESS -p c=NEON

stratum+tcp://cryptopool.cash:3531 -u NEON_ADDRESS -p c=NEON

stratum+tcp://cryptopool.party:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://freepool4all.com:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://mine.thepool.life:9619 -u NEON_ADDRESS -p c=NEON

stratum+tcp://pool.jadecoin.net:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://asic.hashncash.net:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://progpool.hopto.org:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://smithpool.dynu.net:3533 -u NEON_ADDRESS -p c=NEON

stratum+tcp://usa.thecryptominerpool.com:3560 -u NEON_ADDRESS -p c=NEON








stratum+tcp://bigmine.org:3944 -u NEON_ADDRESS -p c=NEON,m=solo






                   
























                   






MCT.Plus
Wadax.io
CoinExchange







NEON Website
http://nucleon.cc

NEON/BTC Market
http://btc.nucleon.cc

NEON/ETH Market
http://eth.nucleon.cc

NEON/ENY Market
http://eny.nucleon.cc

NEON Wallet Downloads
http://wallets.nucleon.cc

NEON Source Code
http://github.nucleon.cc

NEON Discord Server
http://discord.nucleon.cc

NEON Bitcointalk Thread
http://bitcointalk.nucleon.cc

NEON on Twitter
http://twitter.nucleon.cc

NEON on YouTube
http://youtube.nucleon.cc

NEON Block Explorer
http://explorer.nucleon.cc

NEON Mining Statistics
http://miningstats.nucleon.cc

NEON Masternode Statistics
http://masternodestats.nucleon.cc

NEON Shared Masternode Hosting
http://hosting.nucleon.cc









The OP has been redone
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node

that's the point
cannot get to sync daemon
member
Activity: 210
Merit: 20
https://onlydoge.fans/
legendary
Activity: 2548
Merit: 1054
CPU Web Mining 🕸️ on webmining.io
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?

Windows Qt for this node
sr. member
Activity: 664
Merit: 250
done but 15 connections, no blocks...

Code:
{
  "version": 2020000,
  "protocolversion": 70211,
  "walletversion": 61000,
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 0,
  "timeoffset": 0,
  "connections": 15,
  "proxy": "",
  "difficulty": 0.000244140625,
  "testnet": false,
  "keypoololdest": 1549018443,
  "keypoolsize": 999,
  "paytxfee": 0.00000000,
  "relayfee": 50.00000000,
  "errors": ""
}

any idea?

Close the wallet and reopen it (please ONLY delete debug.log before doing this so it is a fresh debug log for me to review if this doesn't work)

Code:
receive version message: /Nucleon Core:2.2.0/: version 70211, blocks=11084, us=46.226.108.74:47000, peer=0
2019-02-05 15:59:27 ERROR: ContextualCheckBlockHeader : incorrect proof of work (VRX pre-fork) - 118467.027391 236934.003725 118466.976334 at 6715
2019-02-05 15:59:27 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000001c61cea721873129e21612deedb5f8961c1d0bf6eed207b4d284, bad-d$
2019-02-05 15:59:27 Misbehaving: 207.246.86.188 peer=0 (0 -> 100) BAN THRESHOLD EXCEEDED
2019-02-05 15:59:27 ERROR: invalid header received

I'm going to try syncing a node from 0 right now. What block are you stuck on this time?

EDIT: I'm already synced up with that node. Please make sure you have the latest wallet from http://wallets.nucleon.cc

daemon?
Pages:
Jump to: