|
11
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] The Nibble (NBL) Trade On Cryptsy.com **Update Your Conf File***
|
on: May 29, 2013, 04:19:21 AM
|
|
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.
|
|
|
|
|
12
|
Alternate cryptocurrencies / Altcoin Discussion / Re: Think about what Attcking nibble will achieve ....
|
on: May 28, 2013, 10:34:25 PM
|
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.
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. I didn't say I couldn't - I am working on it... |
|
|
|
|
14
|
Alternate cryptocurrencies / Altcoin Discussion / [ATTN] Nibble (NBL) - Please Add These Nodes to your nibble.conf
|
on: May 28, 2013, 07:07:26 PM
|
|
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!
|
|
|
|
|
17
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] The Nibble (NBL) - 21 million units - NO Pre-mine - Trade On Cryptsy.com
|
on: May 28, 2013, 06:43:04 PM
|
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 <<EOF 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. you don't need all those things 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. |
|
|
|
|
Show Posts
