Topic: i quit - page 70. (Read 142560 times)
If same hardcoded nodes are kept it will continue to fork as they are no good, I think the best is my solution with new nodes and random chain
also would be great if spooky share his findings 
so we are not messing up each other code
so we are not messing up each other code 
Lol Peter you are ok? Im not speak with you now lol,better say why when you here that you start nervious?. Its now show all connection like local network with different internal IP. But with the same local adress.
lol
Check these: litedoge / src / chainparams.cpp
vSeeds.push_back(CDNSSeedData("198.105.125.233", "198.105.125.233"));
vSeeds.push_back(CDNSSeedData("198.105.125.234", "198.105.125.234"));
vSeeds.push_back(CDNSSeedData("198.105.122.174", "198.105.122.174"));
did
seednode1
***:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.102.172",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429101372,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
seednode2
****:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.4.12",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429108212,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
now both seednodes and my wallet are on same fork
So does the community want to continue from this fork?
I think the best is to go with the block explorer chain.. Minerftw and I and got it working and it also syncs nice with the block explorer. I feel goin with this chain is the best solution if there is one in this case.. If we roll back to 40001 then all the transaction that occurred on exchanges are a mess.. Not sure what everyone thinks but I for one support goin with the chain the block explorer has been on all along..
If you all agree we can get new wallet made up shortly
Best Regards
d57heinz
Yes. Stick with block explorer. Do not roll back. Roll back will be huge clusterfuck.
Unless there is a wallet that will prevent this massive forking from happening again I guess choosing a fork (and the winners of the fork lotto) is kind of secondary.
With block rewards under 10k, only about 13.5 million LDOGE are created a day. There are nearly 2.75 Billion LDOGE out there right now so while shitty, it really is a minor detail. Also, its not like there is active scamming going on here. It would have to be the least lucrative and most pointless scam in crypto history. Some people are just going to be lucky and have their blocks accepted as valid. Some are going to lose a whole day of staking. Finally there is the issue that the LDOGE market was open to trading, deposits, and withdrawals for a time before the forking was being widely acknowledged. This will turn into an epic clusterfuck if bittrex is asked to roll back the market. Best thing for LDOGE is just get this issue fixed as soon as possible and move on.
Give me your LDOGE address and I will send you 1 million once the network is chugging along again.
Just release it.
There is not much choice at this point.
As is no coins are good.
There is not much choice at this point.
As is no coins are good.
Thats the hardest part though. if we release a fix we doing it first need all wallets to be down. and exchanges need to get updated version also etc etc.
Just release it.
There is not much choice at this point.
As is no coins are good.
There is not much choice at this point.
As is no coins are good.
Lol Peter you are ok? Im not speak with you now lol,better say why when you here that you start nervious?. Its now show all connection like local network with different internal IP. But with the same local adress.
lol
Check these: litedoge / src / chainparams.cpp
vSeeds.push_back(CDNSSeedData("198.105.125.233", "198.105.125.233"));
vSeeds.push_back(CDNSSeedData("198.105.125.234", "198.105.125.234"));
vSeeds.push_back(CDNSSeedData("198.105.122.174", "198.105.122.174"));
did
seednode1
***:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.102.172",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429101372,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
seednode2
****:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.4.12",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429108212,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
now both seednodes and my wallet are on same fork
So does the community want to continue from this fork?
I think the best is to go with the block explorer chain.. Minerftw and I and got it working and it also syncs nice with the block explorer. I feel goin with this chain is the best solution if there is one in this case.. If we roll back to 40001 then all the transaction that occurred on exchanges are a mess.. Not sure what everyone thinks but I for one support goin with the chain the block explorer has been on all along..
If you all agree we can get new wallet made up shortly
Best Regards
d57heinz
Unless there is a wallet that will prevent this massive forking from happening again I guess choosing a fork (and the winners of the fork lotto) is kind of secondary.
My fork will work, ot has 2 new seed nodes and I am not tje winner of the fork lotto 
i took explorer version as guide point. it is working and not hanging how i changed code and staking working like it should be.
i hope dev want to stay on same chain also. otherwise we fixed nothing
Can you help me with my wallet.dat situation?i hope dev want to stay on same chain also. otherwise we fixed nothing
I can help you, but cannot do it right now because I am at home. I will be at work about 11 hours from now.
Unless there is a wallet that will prevent this massive forking from happening again I guess choosing a fork (and the winners of the fork lotto) is kind of secondary.
Lol Peter you are ok? Im not speak with you now lol,better say why when you here that you start nervious?. Its now show all connection like local network with different internal IP. But with the same local adress.
lol
Check these: litedoge / src / chainparams.cpp
vSeeds.push_back(CDNSSeedData("198.105.125.233", "198.105.125.233"));
vSeeds.push_back(CDNSSeedData("198.105.125.234", "198.105.125.234"));
vSeeds.push_back(CDNSSeedData("198.105.122.174", "198.105.122.174"));
did
seednode1
***:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.102.172",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429101372,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
seednode2
****:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.4.12",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429108212,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
now both seednodes and my wallet are on same fork
So does the community want to continue from this fork?
Lol Peter you are ok? Im not speak with you now lol,better say why when you here that you start nervious?. Its now show all connection like local network with different internal IP. But with the same local adress.
lol
Check these: litedoge / src / chainparams.cpp
vSeeds.push_back(CDNSSeedData("198.105.125.233", "198.105.125.233"));
vSeeds.push_back(CDNSSeedData("198.105.125.234", "198.105.125.234"));
vSeeds.push_back(CDNSSeedData("198.105.122.174", "198.105.122.174"));
did
seednode1
***:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.102.172",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429101372,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
seednode2
****:~# litedoged getinfo
{
"version" : "v1.0.0.1-g32a928e",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 41744,
"timeoffset" : 0,
"moneysupply" : 2795795175.26000023,
"connections" : 3,
"proxy" : "",
"ip" : "104.236.4.12",
"difficulty" : {
"proof-of-work" : 153.05769441,
"proof-of-stake" : 17550.91418040
},
"testnet" : false,
"keypoololdest" : 1429108212,
"keypoolsize" : 101,
"paytxfee" : 0.99000000,
"mininput" : 0.00000000,
"errors" : ""
}
Are you planning to roll back to block 40k? I think no matter which fork you call the correct fork it will provide an unfair advantage to whoever was on it since they will have mined all of the blocks on it.
someone will have extra luck That doesn't really address the problem. In two days I had staked 200% of what I had in my wallet to begin with and I already had quite a lot. If the fix is just a giveaway to a few then this coin is fucked.
so you staked wrong. you staked orphans then. so you say because all others on other chain/fork or whatever that your 200% is normal and not a few lucky stakes? If others weren't on other chains then you should't get these you did either with normal network weight etc
What I am a saying is that the network fractured into so many chains that whoever is on the one that is chosen as "correct" going forward had way more weight then they should have. Just to prove the point I have now restarted my wallet and synced it with the chain that the block explorer is on. I now see that I am expected to stake every 5 minutes. Before the network forked so badly I was expected to stake about every 9 hours. So if we choose the chain the block explorer is on as the "correct" chain then whoever has been on this chain all along has been staking way higher than they should have for 2 days and if we stick with this then I am staking way higher than I should be right now.
EDIT: just got my first block
i took explorer version as guide point. it is working and not hanging how i changed code and staking working like it should be.
i hope dev want to stay on same chain also. otherwise we fixed nothing
Can you help me with my wallet.dat situation?i hope dev want to stay on same chain also. otherwise we fixed nothing
I can help you, but cannot do it right now because I am at home. I will be at work about 11 hours from now.
i took explorer version as guide point. it is working and not hanging how i changed code and staking working like it should be.
i hope dev want to stay on same chain also. otherwise we fixed nothing
Can you help me with my wallet.dat situation? i hope dev want to stay on same chain also. otherwise we fixed nothing
Are you planning to roll back to block 40k? I think no matter which fork you call the correct fork it will provide an unfair advantage to whoever was on it since they will have mined all of the blocks on it.
someone will have extra luck That doesn't really address the problem. In two days I had staked 200% of what I had in my wallet to begin with and I already had quite a lot. If the fix is just a giveaway to a few then this coin is fucked.
so you staked wrong. you staked orphans then. so you say because all others on other chain/fork or whatever that your 200% is normal and not a few lucky stakes? If others weren't on other chains then you should't get these you did either with normal network weight etc
Are you planning to roll back to block 40k? I think no matter which fork you call the correct fork it will provide an unfair advantage to whoever was on it since they will have mined all of the blocks on it.
someone will have extra luck That doesn't really address the problem. In two days I had staked 200% of what I had in my wallet to begin with and I already had quite a lot. If the fix is just a giveaway to a few then this coin is fucked.
ProcessBlock: ORPHAN BLOCK 751, prev=cbbb5407dfefd8704ea60d79c5e6142015721484f1a36b009f9d11201cfdc8d4
receive version message: version 60015, blocks=41254, us=[2001:0:5ef5:79fd:2041:d4:7fb8:ac3e]:17014, them=173.24.12.46:17014, peer=[2001:0:9d38:90d7:2c31:13da:52e7:f3d1]:57255
Added time data, samples 44, offset +5 (+0 minutes)
ProcessBlock: ORPHAN BLOCK 751, prev=81302fc3896f9c6cbd7e15879934c9ece1d7912bf0152e8e1b3f3e149d70f0ee
ProcessBlock: ORPHAN BLOCK 751, prev=066e9a3c64bc4ef3c76b0fe261940b4388c16b9c96252082d431bbbd5070a8ac
ProcessBlock: ORPHAN BLOCK 751, prev=0057fc9e86b664af7f3fdb61151578461280c5d5951c538915d70bd31f70f8c9
ProcessBlock: ORPHAN BLOCK 751, prev=928d273e15c1378f25044347d9b155a9bdeab04e23ef550620ef3410fb3ce455
ProcessBlock: ORPHAN BLOCK 751, prev=755cae36826f194d7afb58d6a2151d35626e4cac00fcc8581e295854c81e6f5d
ProcessBlock: ORPHAN BLOCK 751, prev=d3c7347aaa2f9e525b4a376bd3ade40a51ef951916da6377b600c77a4698577a
ProcessBlock: ORPHAN BLOCK 751, prev=4f513f7cb8e6350545e579f179dcc8c38f6f2470148c96af599e8142e43a3171
ProcessBlock: ORPHAN BLOCK 751, prev=a106e48f48d9f3e0cf5e4afb978e528db7a60efe15a1956d240f5b9a141f9f9d
ProcessBlock: ORPHAN BLOCK 751, prev=2639e30ba07708ce12ed069ad5c7a06241e3e5ac8611010022ac0cd57ee04a17
ProcessBlock: ORPHAN BLOCK 751, prev=f3d16866d06ab2bef737580d752bea79d6fcd263deb74562d5b15472d4dc3bb5
ProcessBlock: ORPHAN BLOCK 751, prev=5d58166a6b6ccf03c9a5e648e15099747782e86db8a8c047e87be0c531601e14
ProcessBlock: ORPHAN BLOCK 751, prev=9b09e00356900af91ec48cffa8bf21d5ccfdfe7c3b259305131fda96b19e8ee1
ProcessBlock: ORPHAN BLOCK 751, prev=0b54ae7290595cdd99b3b382888ef8b89c4bdc322eb2d4d02698ec0c07284237
ProcessBlock: ORPHAN BLOCK 751, prev=04cd03038cdab90e9f452138e70f90d4a3e94337ff2687299cfc3056273e1fec
ProcessBlock: ORPHAN BLOCK 751, prev=b023d5750346dd6a515c18d5d137a4d7edb5c8c76359a689a192322683b95ac4
ProcessBlock: ORPHAN BLOCK 751, prev=16e1e0b7ce4370e4d9817ddc60408b7f0dae9607ba0d75e77a08a081c6c60e87
ProcessBlock: ORPHAN BLOCK 751, prev=a21fefac2663992072b93ae323d97fca27d151e07a96122b3e878e70ccd7d451
ProcessBlock: ORPHAN BLOCK 751, prev=d83544a1d178634860f6cbb6902596d851505df005ce17f27e29225c5c19985a
ProcessBlock: ORPHAN BLOCK 751, prev=9499cf44b814fbcd9bed99c581342c5d6a258edbb3bb161082c5fca597d6bf89
ProcessBlock: ORPHAN BLOCK 751, prev=9fae20026b5542323f0d053f9493621426639b8f0d012ccc2fcdee25bbe0fc08
ProcessBlock: ORPHAN BLOCK 751, prev=882705ca731acbcb88cb4d938360c3bb99ba6ac2745a4a8d7f3ba94af8cf51dd
ProcessBlock: ORPHAN BLOCK 751, prev=408a079de39d935818b4323353c87bec13fc187a661b4a803513c896c4df1322
ProcessBlock: ORPHAN BLOCK 751, prev=10778c1905c6d141ae962286c8d6de813ee7a776f70dc0fabbacb63c717eaa3b
ProcessBlock: ORPHAN BLOCK 751, prev=928d273e15c1378f25044347d9b155a9bdeab04e23ef550620ef3410fb3ce455
ProcessBlock: ORPHAN BLOCK 751, prev=61c071c9840d002ea09e5d2ed1e22748df00b9f1ad7584cc64afd553ebb84170
ProcessBlock: ORPHAN BLOCK 751, prev=9f0bd5387ab7ac61752145d8db2f72e287efe1e4c365801b72ba17f2d2d037f7
ProcessBlock: ORPHAN BLOCK 751, prev=d2fd81d1738a0db638fd80a97453e10fe0c798131cf0fed41580a8a155142204
ProcessBlock: ORPHAN BLOCK 751, prev=ea007b4094e7309fec0ace140a90a56fb748e28c49cb81799b2d1cc7b481fbce
ProcessBlock: ORPHAN BLOCK 751, prev=7d21bd14e91fe21aa64d17b9339794e7056092de1d4169f68fb16657ad12c97c
ProcessBlock: ORPHAN BLOCK 751, prev=07fb592580cd1a3dbccf82b5ed7aaa67728ec34ec0fe84ffc5ad99e1b8bafda4
ProcessBlock: ORPHAN BLOCK 751, prev=b379819782270380d81b1c9089904c39c51d00a712dd798b3d4b42c028180dc6
ProcessBlock: ORPHAN BLOCK 751, prev=68674ed09483fee6e3b55eaefc7002b0be62ea189326f4c40406863ece05b3c7
ProcessBlock: ORPHAN BLOCK 751, prev=db074380f2769f6c655dd466c155cf36438af4401cc6b62bae00aaf578799e73
ProcessBlock: ORPHAN BLOCK 751, prev=de64daa5227e180a761e7d3b2e3c0890fb8470bd55be73e934b3cfe67e51087c
ProcessBlock: ORPHAN BLOCK 751, prev=e07d62a54c26960e0468c5956b4fb1c260fc7c5802be555cba4268585e13de14
ProcessBlock: ORPHAN BLOCK 751, prev=6fa459a668e72073604f9217814a28c195370c23b6676da366bfaf7ac539f2ac
ProcessBlock: ORPHAN BLOCK 751, prev=128381544dc4f1ec58029170f9e99f61a20b04c0461cdd8e2d36099997e48be3
ProcessBlock: ORPHAN BLOCK 751, prev=bf29ad24752b03666d53dc06febcaa99faaf341ae2e54459c579910d69ff77a1
ProcessBlock: ORPHAN BLOCK 751, prev=10778c1905c6d141ae962286c8d6de813ee7a776f70dc0fabbacb63c717eaa3b
ProcessBlock: ORPHAN BLOCK 751, prev=928d273e15c1378f25044347d9b155a9bdeab04e23ef550620ef3410fb3ce455
ProcessBlock: ORPHAN BLOCK 751, prev=23e8f7bea4ba3efec59564118dbed3cc9d5d12d1e1ce792676283e68299a9075
ProcessBlock: ORPHAN BLOCK 751, prev=bd1209480b5b215fd0e66f1e8ca880dea3387e4253cda654e3a45d180e25dda5
ProcessBlock: ORPHAN BLOCK 751, prev=99c890114fee466d375feb6b906fb71c40fa8922c5d495a9a26271ac0204acc1
ProcessBlock: ORPHAN BLOCK 751, prev=729d8246c350d097d274906a8a3d688921ed94dad3a2a994f0e3776b23492bcb
ProcessBlock: ORPHAN BLOCK 751, prev=f3c1ef47cde5176af929c742d0fedf5564ed541f087dd40b7933f1410654b56e
ProcessBlock: ORPHAN BLOCK 751, prev=9811666f7bb51f945d30f2b2cd9d19b13cfe984e400699e4d36c30d1078e737e
ProcessBlock: ORPHAN BLOCK 751, prev=ad6ea6f1383528062a1955aca957e25071f68ba0f0aecaf14ad17eeb7c4c6e04
ProcessBlock: ORPHAN BLOCK 751, prev=f98e841cc1203d86d2ef510de1778e47fafd88c25fca01c3be7080a945c32db4
ProcessBlock: ORPHAN BLOCK 751, prev=726874b21a11a9a7606578ab39f54263ad634c0461a985ef3ba4b437b73d70ad
ProcessBlock: ORPHAN BLOCK 751, prev=c98b10d936a75b211be92219ff187e3874b932d6c2fa937c1c39422cdf7b79bc
ProcessBlock: ORPHAN BLOCK 751, prev=c82ad8a85587bdc8fe1377b27ae861311a02c2b5cba94d7275fcab69146781a7
ProcessBlock: ORPHAN BLOCK 751, prev=b1c1563fbd937ce1c379d9849e1e7a1f60755cabe0e2fd9a1760c88e6ada6a4a
ProcessBlock: ORPHAN BLOCK 751, prev=8a6a76e652ed6e349745a527393aeed3d4fb3d9330152970e326ced3c22cc926
ProcessBlock: ORPHAN BLOCK 751, prev=484cc2572d801f9fc1d8b847e0e82f14279510515bccd87be9ae4d1cbce7214a
ProcessBlock: ORPHAN BLOCK 751, prev=89c3b1fc7df0311150b6c242aadd559770f53c153ca89de9e9b9502d81a63833
ProcessBlock: ORPHAN BLOCK 751, prev=5036e9d9346806002803c8d697dc18aa07deb02a050ae6dfe7b683bb4429b40d
ProcessBlock: ORPHAN BLOCK 751, prev=9850ffdd4f2dec7db9c667a22bb69aa406fda8178532a3ba5518143b3c75d561
ProcessBlock: ORPHAN BLOCK 751, prev=2acfab5e6cc81c1a3c54bd6ba5afeafb42f95951c4ac1d8f10d3548a2f0f6ec4
ProcessBlock: ORPHAN BLOCK 751, prev=9b0133941e5d01a9708f91401611bdd61e36307491b4c384bc4fcd86dcf64601
ProcessBlock: ORPHAN BLOCK 751, prev=b2a3ed1347b96e0794ae5d80b43ac9ba1a694158df636b5d5b8ae6bcb23be7a2
ProcessBlock: ORPHAN BLOCK 751, prev=f47da4923722e4b92a5b5fab95bc150f5dfa4457d377a99eceec6f9b8708294d
ProcessBlock: ORPHAN BLOCK 751, prev=88825133cec4b07e9fe2a3dacfaa9e52787963a9a9833ca1e4ae2a3460cfdda2
i took explorer version as guide point. it is working and not hanging how i changed code and staking working like it should be.
i hope dev want to stay on same chain also. otherwise we fixed nothing
You are not need here block explorer. All transaction in database anyway. Since launch. Yes you are right its can down again in any time. i hope dev want to stay on same chain also. otherwise we fixed nothing
Are you planning to roll back to block 40k? I think no matter which fork you call the correct fork it will provide an unfair advantage to whoever was on it since they will have mined all of the blocks on it.
someone will have extra luck Lol Peter you are ok? Im not speak with you now lol,better say why when you here that you start nervious?. Its now show all connection like local network with different internal IP. But with the same local adress.
lol
Check these: litedoge / src / chainparams.cpp
vSeeds.push_back(CDNSSeedData("198.105.125.233", "198.105.125.233"));
vSeeds.push_back(CDNSSeedData("198.105.125.234", "198.105.125.234"));
vSeeds.push_back(CDNSSeedData("198.105.122.174", "198.105.122.174"));
Jump to: