Search content
Sort by
Showing 20 of 142 results by hyoshi
Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
holy shit hyoshi is calling in the feds !
hey hyoshi a full config example can we put it up on the top there?
from here on in 10% of all nibble & Hellokittykoin transactions go to the FBI.
: D
LOL just kidding, would never do thathey hyoshi a full config example can we put it up on the top there?
from here on in 10% of all nibble & Hellokittykoin transactions go to the FBI.
: D
Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
nibble in computing = 4 bits
21,000,004 total nibbles
mind=blown
4 bits bigger than bitcoin21,000,004 total nibbles
mind=blown
Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
lulz that would be my bad
Re: [ATTN] Nibble (NBL) - Please Add These Nodes to your nibble.conf
If you add these lines, you should NOT get re-sync issues from the jealous people trying to destroy this and other coins.
I am working on additional nodes, and additional security measures that would disconnect and ban these misbehaving nodes immediately. Just trying to be careful as it is a powerful thing to do.
Also thinking of a way to prevent difficulty attacks.
I am working on additional nodes, and additional security measures that would disconnect and ban these misbehaving nodes immediately. Just trying to be careful as it is a powerful thing to do.
Also thinking of a way to prevent difficulty attacks.
Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
lol you copied the twitter icon for your currency?
Yeah its the same, identical, all birds = twitter. Buy some now, and get rich later.This is beginning to smell a lot like Solidcoin 3.0 to me!
~BCX~
nah I have this under control ~BCX~
Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
I updated the main page of the thread - everyone add this to your nibble.conf file ASAP:
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
As we add additional trusted nodes, we will change he value of "maxconnections". The reasoning being this is that we should only connect to trusted peers or at least peers that are operating within the parameters of the network. Otherwise, if you allow a large number of peers, you risk getting a misbehaving peer.
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
As we add additional trusted nodes, we will change he value of "maxconnections". The reasoning being this is that we should only connect to trusted peers or at least peers that are operating within the parameters of the network. Otherwise, if you allow a large number of peers, you risk getting a misbehaving peer.
I just don't get what they hope to achieve.
No way they can be successful. They just make it annoying if you are running the QT client for any reason. Key is though to keep clients running. Let the IP's get banned. If you shut down the client and re-open it, it will not remember the ban.
No way they can be successful. They just make it annoying if you are running the QT client for any reason. Key is though to keep clients running. Let the IP's get banned. If you shut down the client and re-open it, it will not remember the ban.
Maybe their mission is to force you to fix the code to make these attacks not impact your coin.
When the 'developer' (that's you) tells his users to 'keep clients runnning' because 'If you shut down the client and re-open it, it will not remember the ban' then you know that the coin is doomed.
I mean, why is the ban list not stored to a file, for instance?
I wonder if you have the skills to be the lead developer of a crypto.
The ban is not stored in a file in any crypto at the moment dunce - the above is the same with bitcoin on down
So you, as the developer, say that you can't implement a nessecary security feature because none of the other cryptos have implemented it?
LOL
And you call me a dunce?
FWIW, the other crypto's don't need to restart their clients to get rid of rougue peers. Don't expect them to fix this. Since you're the nibble dev it is up to you to implement a solution, it is not up to the other cryptos.
[ATTN] Nibble (NBL) - Please Add These Nodes to your nibble.conf
I updated the main page of the thread - everyone add this to your nibble.conf file ASAP:
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
As we add additional trusted nodes, we will change he value of "maxconnections". The reasoning being this is that we should only connect to trusted peers or at least peers that are operating within the parameters of the network. Otherwise, if you allow a large number of peers, you risk getting a misbehaving peer.
More to come - these are just a start.
Windows: %appdata%\nibble\nibble.conf (create the file if you don't have one)
Nix: ~/.nibble/nibble.conf
We need additional trusted nodes, so anyone running a pool, if possible please allow/forward port 8550, and anyone else who can just run a dedicated node, please provide the IP of your node (again if port 8550 is allowed inbound or forwarded).
Thanks!
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
As we add additional trusted nodes, we will change he value of "maxconnections". The reasoning being this is that we should only connect to trusted peers or at least peers that are operating within the parameters of the network. Otherwise, if you allow a large number of peers, you risk getting a misbehaving peer.
More to come - these are just a start.
Windows: %appdata%\nibble\nibble.conf (create the file if you don't have one)
Nix: ~/.nibble/nibble.conf
We need additional trusted nodes, so anyone running a pool, if possible please allow/forward port 8550, and anyone else who can just run a dedicated node, please provide the IP of your node (again if port 8550 is allowed inbound or forwarded).
Thanks!
Re: [ANN] The Nibble (NBL) - Trade On Cryptsy.com - More Profitable than Bitcoin!
Some pools report a false hashrate. These two work fine:
cgminer --scrypt -o next.afraid.org:8118 -u yourNBLaddress -p . --queue 0 -s 1
cgminer --scrypt -o pool.1nusa.org:8118 -u yourNBLaddress -p . --queue 0 -s 1
cgminer --scrypt -o next.afraid.org:8118 -u yourNBLaddress -p . --queue 0 -s 1
cgminer --scrypt -o pool.1nusa.org:8118 -u yourNBLaddress -p . --queue 0 -s 1
Anyway, Nibble has an issue, the difficulty is far higher that we can expect. Difficulty=3.99, the hasrate is only 46MH/s.
A feathercoin like issue?
Re: [ANN] The Nibble (NBL) - 21 million units - NO Pre-mine - Trade On Cryptsy.com
i want to mine in solo, what is the port?
You have to edit or add a .conf file, e.g. under unix:
mkdir -p ~/.nibble/;cat >~/.nibble/nibble.conf <server=1
rpcuser=nibblecoin
rpcpassword=YourPassword
rpcallowip=127.0.0.1
rpcport=18341
#addnode=machine...
EOF
chmod 600 ~/.nibble/nibble.conf;
This file is required, to setup a password and an user account. In that case the port is set to 18341.
just set user pass and server in the confing
and make a bat with all the info (config info, plus tc and host:port)
it work like a charm with litecoin
i just need the port, hence why i asked, thank you anyway
mmh, it doesn't work...
The rpcport can be ANYTHING - I use 8000, because then I can easily switch between mining daemons while my miners continue to use the same user/pass and port.
Re: [ANN] The Nibble (NBL) - 21 million units - NO Pre-mine - Trade On Cryptsy.com
Please add the following (we need a lot more but use these for now) to your nibble.conf file:
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
addnode=99.132.231.140
addnode=72.11.149.185
addnode=207.12.89.2
addnode=46.39.246.24
addnode=54.244.198.104
addnode=72.78.100.3
addnode=106.187.94.209
maxconnections=5
Re: [ANN] Nibble Now Traded on Cryptsy.com - Buy Them While They're Cheap!
With constant attacks, doesn't that bring the reliability of nibble, into question?
No, but it brings to mind that some of these attacks are traceable, and likely perpetrated by youhow to put it in conf?
or if im a node i don't need to do anything?
here is a good node: 207.12.89.2
Add it to your conf file like this (just add a line at the bottom, save and restart your daemon/walet):
addnode=207.12.89.2
I have someone in network security that may be able to help - i'll ask.
how do you distinguish right from wrong nodes?
And what will be if bad node masked as a good node, then switches to the bad node?
And what will be if bad node masked as a good node, then switches to the bad node?
Then we will remove them. Its easy to tell. You look in the config file and see if they are trying to cram 300K worth of block onto the network. There are other ways as well, and I will be verifying them.