Who owns these IP's?? 188.166.35.49 and 68.172.251.98 Update your Wallets stragglers...  |
|
|
|
|
what are your IP addresses on your Masternodes? PM them to me
|
|
|
|
|
We are working on some New stuff, but it doesn't happen over night. It is a process. Enjoy the ride.
|
|
|
|
Now we know where we are standing among all the other coins. 8BTC marketcap is pretty low for a capable coin. Good time to mine/buy now. Don't go and buy out those buy walls, put your orders on the sell side and wait for the dumpers. Dev, We need to polish the OP. Is this coin really capable of anonymous transaction, I am still confused. What does the obfuscate button do?. I am sorry if I sound naive, I have never used Dash coin  . It will help new comers if you can prepare a white paper. Yes, there is still much to do, but we are only 2 people and it will take time... I said that this coin is here for the long road, not the get rich quick and then dump scene. "Obfuscation" is a Mixing service build in to the Network. you can use it to hide your coins origins as they will be sent all over the network through the Masternodes and back to your wallet making them untraceable. We are also working on a few other items that will also ad another layer of privacy to the network. We will release these items shortly before they are to be released. s3v3n |
|
|
|
Anyone familiar with Raspberry Pi's? Trying to compile PayCon on my RPi2, haven't had much luck so far
If your main concern is to secure your Paycon and get stake rewards I would suggest a Steps StaySafe wallet. I've been staking all of my Paycon for weeks and I don't even have to have my computer on. There is also a Steps StaySafe wallet for Colossuscoin. altcoinsteps.com Jahvinci, Pm me and I can give you much more details about it as well as tips to get the maximum amount of stakes a day! Cloud staking is surely convenient, but not sure how it could be considered to be secure, when all your coins are at discretion of someone else, and there is no guarantee that person will not make a runner with all your coins some day...  . Or they can be "hacked"... I don't tell they will, but given the absence of any regulation in crypto, nothing stops them by doing so. There were so many cases... Even supposedly "reputable" exchanges sometimes get "hacked"  Related to RPi2, I never had one, but I compiled many wallets for other Debian Linux-based ARM devices without issues. Could help you with this if you have some specific issue/question. search stakebox on github to get your RPi2 Con wallet precompiled |
|
|
|
|
What other things are in the works to increase TEK's value??
|
|
|
|
If no one noticed, Presstab put up a Darknet block explorer.. Link is on the ANN Thank You @Presstab!! |
|
|
|
the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.
Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.
So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..
Theoritical question: if I know the IP address of a masternode that is not mine and start my own masternode with his address as my masternodeaddr, does it mean I can ban both him and myself? No, you would need their information from their Controller wallet, as their MN key is just to verify that a wallet is running out there as a Masternode |
|
|
|
|
yeah, I consider it growing pains until the network can grow to a more stable size. Thanks for sticking with us. The network is real fragile in the beginning
|
|
|
|
|
the issue stemmed from the Pool/blockexplorer was banned for some reason (We are researching the specific reason) but essentially had a misbehaving masternode at the same IP as the pool/blockexplorer. So the network banned his IP, so his wallet connected with a few other iP's that were also banned and created their own little temp network where the blocks were all 250 DNET because their little network did not have any masternodes on it to trigger the 20%/80% split that the reward does on the correct network. but those of use who were mining that pool, got orphans because when the pool handed out the 250 DNET blocks only to the miner, then Network enforced the Reward rules and Orphaned those blocks.
Until We figure out why his IP was banned other than a misbehaving Master node, it is important that people follow the rules of 1 public IP per masternode or the network will ban your IP and any wallet that is also attached to that banned IP which is what ended up happening.
So no, the Block Explorer is not up to date at the moment, it should be back online tomorrow sometime. Sorry Guys..
|
|
|
|
|
There were some blocks, after the blockchain started moving again, that were orphaned until everyone restarted their master node and the network caught back up. everything seems to be moving along fine now
|
|
|
|
Yep lost connection to the network and a couple thousand coins in the process on that deal. I'll point one of my cards to a pool if it keeps that from happening again.
couple thousand coins how? |
|
|
|
|
Thanks OC!!
Everyone needs to do a masternode start-all as your masternodes expired while the chain stalled..
Thanks!!
|
|
|
|
|
OK guys, I need everyone to turn on their wallet solo-mining just incase
Please everyone add gen=1 to your darknet.conf file. it will help keeping the hash decentralized so this doesn't happen again.
The issue was caused by too much hash being on one pool, and that pool went down. so the blockchain stalled. Stakebox and Myself have put some hash at several of the pools for the next few days to keep it going.
Sorry for the issues..
KEEP MINING!! Please
|
|
|
|
|
We are looking into the stall. We know one of the pools went down earlier at that time.
|
|
|
|
Try the darknet-qt in src/qt.
Add the nodes from op. My win wallet didn't need the addnodes, the linux one didn't connect without.
Thank trying to do this but need to build from source to get that darknet-qt to show up in src/qt... tried building from source and got this error/output stream: Making all in src
make[1]: Entering directory `/root/Darknet/src'
make[2]: Entering directory `/root/Darknet/src'
CXX libbitcoinconsensus_la-allocators.lo
CXX primitives/libbitcoinconsensus_la-transaction.lo
CXX crypto/libbitcoinconsensus_la-hmac_sha512.lo
CXX crypto/libbitcoinconsensus_la-sha1.lo
CXX crypto/libbitcoinconsensus_la-sha256.lo
CXX crypto/libbitcoinconsensus_la-sha512.lo
CXX crypto/libbitcoinconsensus_la-ripemd160.lo
CXX libbitcoinconsensus_la-eccryptoverify.lo
CXX libbitcoinconsensus_la-ecwrapper.lo
CXX libbitcoinconsensus_la-hash.lo
CXX libbitcoinconsensus_la-pubkey.lo
CXX script/libbitcoinconsensus_la-script.lo
CXX script/libbitcoinconsensus_la-interpreter.lo
CXX script/libbitcoinconsensus_la-bitcoinconsensus.lo
CXX libbitcoinconsensus_la-uint256.lo
CXX libbitcoinconsensus_la-utilstrencodings.lo
CXXLD libbitcoinconsensus.la
CXX darknetd-darknetd.o
g++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
make[2]: *** [darknetd-darknetd.o] Error 4
make[2]: Leaving directory `/root/Darknet/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/Darknet/src'
make: *** [all-recursive] Error 1
Any ideas?  did you use the install script that I provided to compile and install all the Deps etc? then auto-compile everything for you?? You can also use the precompiled Linux binaries I have provided as well if you download the precompiled binaries, there is also a script to install all the required Deps before you can use those binaries. |
|
|
|
on my wallet i setted mastenode address ... now i send from my address to masternode address exctly 10000 dnet ... i apply complete procedure for run masternode but when in console write masternode start the result is " Not capable masternode: Can't detect external address. Please use the masternodeaddr configuration option."
why???
i can set masternode in my wallet if i have in totally 13000 dnet ... and sended 10000 to my mastenode address created... why not work?
thanks
You missed a step, Your router MUST have port 51472 open or you will get this error |
|
|
|
|
You can Also use Yobit as well, they have been around for longer.
|
|
|
|
Thanks. I have the 51472 port forwarding setup in my router to my PC's DHCP IP and I've edited both masternode & darknet conf files as outlined. Do I need both a controller node and a master node setup for it to work? Also my masternode won't start unless I use the below line also.  masternodeaddr=127.0.0.1:51472 OK, to start with, you can not use duplicate public IP's, internal network IP's or your loopback address's as your MN address's. you need to open port 51472 in your router, and then go to google and search "Whats my IP" don't port forward, just open the port in your firewall.. then use that IP address. secondly, if you are only going to have one Masternode, then you can do everything within your darknet.conf file. if you will have more than one Masternode, you will need to use the darknet.conf file on the remote masternodes, and use the masternode.conf file on the local wallet (Your Controller wallet which holds the actual coins) |
|
|
|
|
Show Posts
