There shouldn't be any connection problems for MOJO. HOdlcoin doesn't connect whatever I do so what I am I meant to do? |
|
|
|
|
Proposed changes in the next MOJO release:
1. Activate and fix Spork system and enable a reference node: This will make MN payments more stable and fairly distributed.
2. Set block time at 5 min. to reduce blockchain size: Recently the block time is around 30 sec. and this will lead to a very large blockchain very quickly.
3. Complete Tor integration so network runs under Tor only: All the nodes and the MNs will run under Tor only.
4. Deactivate PoW blocks.
|
|
|
|
I put in a vote as well for the African fintech awards  |
|
|
|
|
I can't get any connections, I have added all the nodes from the block explorer and let it run for hours but not a single connection???
|
|
|
|
|
I'll put it up later when I get home, in on my phone now
|
|
|
|
Yes, this fucking sucks. I am losing stakes for over a week now. fuck.
That is not possible to lose a stake. Can you give me more infos about that? Christian, he wanted to say: his wallet cannot stake because of this problem, so he is losing money. Its reasonable, but a bit too emotional  Yes, correct. Also, has anyone come up with a "How to setup a Masternode for Noobs" for MOJO yet? I know there was a bounty. Maybe raise it a bit? I would like one for Windows 10 64-bit. I'll even add my own MOJO to the total bounty once this gets done. Thanks. Ok, I raise the bounty: BOUNTY: 200,000 MOJO for Win MN setup (that works on Win 10) |
|
|
|
hmmm very strange.. 0 connections  installed a new wallet to test = NOK If your PC is placed behind a NAT router (no real IP address), then you have exactly the same problem as everybody else here - you connect to nodes, then disconnect from them immediately. Read the last two pages for more information. This is known problem, devs are looking into it. This is an issue that should be given prior importance than any other tasks. If the dev team issue a bounty to this, many people would come and try to find a solution to this. A fix has been applied and I'll sort out new wallets very soon |
|
|
|
my wallet dont connect to a node? i have to add the nodes manually? where i can do that?
There are 3 hard coded seed nodes and they should be up and running, I will check later when I'm back on my other computer. You shouldn't have to add nodes manually. |
|
|
|
|
If every single node running Bitcoin would crash at the same time and they all lost their copy of the Blockchain, would all Bitcons be lost forever?
|
|
|
|
We are looking into it. I have 9 connections now:
We will consider any issues around peer discovery
Does your machine have real IP address, or it is behind NAT router? I suppose it is real IP, right? This is not about peer discovery. I have the same issue other guys are reporting here, and here is what I can add: I tried the wallet on two different windows machines on two different locations - the symptoms are the same. I have put a tremendous amount of "addnode" in my mojocoin.conf, and I would tell - those nodes are indeed being found, but wallet cannot connect to them! I see the "connection" icon in the bottom-right corner is almost blinking, showing 1 peer, then zero, then again 1 peer, then zero again, and so on. The peers are being found, but no connection could be established to them. In debug.log on both machines I see big amount of "socket recv error 10054". Both machines are placed behind routers, which could be the problem, however switching UPNP on/off from the settings did not help. The output is like this: 2016-09-08 16:18:26 socket recv error 10054
2016-09-08 16:18:27 socket recv error 10054
2016-09-08 16:18:27 UPnP: ExternalIPAddress = x.x.x.x
2016-09-08 16:18:27 AddLocal(x.x.x.x:22255,3)
2016-09-08 16:18:28 socket recv error 10054
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:29 UPnP Port Mapping successful.
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:30 socket recv error 10054
2016-09-08 16:18:31 socket recv error 10054
2016-09-08 16:18:32 socket recv error 10054
2016-09-08 16:18:33 socket recv error 10054
2016-09-08 16:18:34 socket recv error 10054
2016-09-08 16:18:35 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:37 socket recv error 10054
2016-09-08 16:18:38 socket recv error 10054
2016-09-08 16:18:39 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:41 socket recv error 10054
2016-09-08 16:18:42 socket recv error 10054
2016-09-08 16:18:43 socket recv error 10054
2016-09-08 16:18:44 socket recv error 10054
2016-09-08 16:18:45 socket recv error 10054
2016-09-08 16:18:46 socket recv error 10054
2016-09-08 16:18:47 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:49 socket recv error 10054
2016-09-08 16:18:50 socket recv error 10054
2016-09-08 16:18:51 socket recv error 10054
2016-09-08 16:18:52 socket recv error 10054
2016-09-08 16:18:53 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:55 socket recv error 10054
2016-09-08 16:18:56 socket recv error 10054
2016-09-08 16:18:57 socket recv error 10054
2016-09-08 16:18:58 socket recv error 10054 BTW, about a week ago the same wallet was synching nicely. This is serious issue, as there are many people already hit by this problem here. Yes, real IP I guess, static IP and so on. Ok, I get it now, we will deal with it. I don't know Windows much but will discuss with Limxdev and others. |
|
|
|
The idea would be that the whole network, i.e. all the nodes, clients, masternodes etc. communicated through Tor and so no traffic would ever reach the clearnet, all transactions within Tor, exclude all clients not running Tor. No traffic would ever reach a Tor exit node.
The point is that the network that has been designed for that, is I2P, and in a certain way, Freenet, not TOR. TOR has this functionality also, but as an ad-on. I2P was designed exactly with that in mind. I was thinking about Freenet because maybe the ledger (block chain) could be a distributed freenet file itself. That's interesting, I will have a look at Freenet and I2P in some more detail and see what might be possible. Do you know any cryptos using Freenet? |
|
|
|
I am trying to do some background research on cryptos w/ integrated Tor or I2P and that run the entire network within Tor or I2P and NOT as an option.
It would be somehow contradictory to run such a thing on Tor. If the idea is to confine it to the network, then I only see I2P as an option, even though you *could* do it on TOR, but it would be a bad idea. TOR is essentially meant to be an obfuscating proxy on the clearnet. Even though you can have hidden services on TOR, it is not meant to be an "inside only" network, and hence compromises have been made on TOR that are not necessary if your goal is to stay inside the net. I would even say that if you don't want to stick to I2P, Freenet is a better idea than TOR. In other words, you take unnecessary risks by using TOR, because TOR is designed to exit back to the clearnet, and has to accept certain risks doing so. I2P doesn't, and is hence IMO safer for an "inside only" network usage. The idea would be that the whole network, i.e. all the nodes, clients, masternodes etc. communicated through Tor and so no traffic would ever reach the clearnet, all transactions within Tor, exclude all clients not running Tor. No traffic would ever reach a Tor exit node. |
|
|
|
I am trying to do some background research on cryptos w/ integrated Tor or I2P and that run the entire network within Tor or I2P and NOT as an option. Can we try to compile a list of coins running Tor only (or I2P only) and what are the weaknesses with such a system and how could it be improved. ED: I have so far found: Cryptographic Triangles [TRI]https://bitcointalk.org/index.php?topic=820103.0https://github.com/wurstgelee/trianglesOnly traded on Cryptopia and seems abandoned, no activity on GitHub for more than a year and dev not online since January 2016 This crypto appears to be running the entire network within Tor Excluding the CryptoNote currencies: Monero (XMR), Bytecoin (BCN), Ducknote (XDN) etc. |
|
|
|
We are looking into it. I have 9 connections now:  We will consider any issues around peer discovery |
|
|
|
|
We have three seed nodes running now:
108.61.172.245
45.63.43.114
45.32.234.45
They are all hardcoded into mojonode01,02,03
I know there was a fork but it resolved itself as it should as the checkpoints are in place. I don't know why there seems to be an issue with peer connections. I will investigate this.
|
|
|
|
|
I don't think the fork was a big problem, the checkpoints works and so it should resolve itself.
If you find specific issues can you please use the GitHub issues section. I opened it up and I will try to document all the issues there for the next update.
|
|
|
|
I got a third seed node up now, should be: 108.61.172.245 or mojonode03.mojocoin.org You shouldn't have to put it in the mojocoin.conf as it's in the code and I have checked the DNS settings and it should all be good:  If anyone is having problems, then try to delete the peers.dat and restart, you should have 3 seed nodes hard coded I have restarted, and now the wallet is syncing, but with the mojonode03: mojocoind getpeerinfo
[
{
"addr" : "108.61.172.245:22255",
"services" : "00000001",
"lastsend" : 1473193019,
"lastrecv" : 1473193019,
"bytessent" : 180545,
"bytesrecv" : 1187107,
"conntime" : 1473193018,
"pingtime" : 0.13114600,
"version" : 90000,
"subver" : "/Mojocore:2.3.0/",
"inbound" : false,
"startingheight" : 113720,
"banscore" : 0,
"syncnode" : true
I'll try to restart the 01 and 02 nodes |
|
|
|
|
Show Posts
