Pages:
Author

Topic: [ANN][MAST] MastCoin | CoinRecycler | Bittrex - page 41. (Read 180288 times)

hero member
Activity: 518
Merit: 500
The blockchain is the future
Can u guys plz make a conf file for me and upload it thx
member
Activity: 98
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.
Well I'm running an Amazon EC2 instance which will not connect. The wallet has been allowed in the firewall. My Windows 8.1 machine is on a different IP and in no way affiliated with the EC2. Both will not connect, both have been allowed through firewall, and both have other coin wallets downloading and syncing as we speak. So it really seems as if there is something wrong. I am going to make a config now and see what happens. Would I name it Mast.conf or MastiffCoin.conf?

Hmm, I see what you're saying now. I installed a new MastCoin wallet onto a fresh directory and it wouldn't sync.

** EDIT: I know what the problem is.. the search/replace for rebranding MastiffCoin to MastCoin in the wallet must have removed the nodes - we'll fix that up and release an updated version soon, sorry for the trouble.

I created a MastiffCoin.conf file with the following nodes, and it sync'd right up though:

addnode=node1.mastiffcoin.com
addnode=node2.mastiffcoin.com
addnode=node3.mastiffcoin.com

We'll investigate why those nodes aren't being sync'd from automatically, because they're the built in seednodes and should work just fine.

To answer your second question, yes the datadir and conf file are under the MastiffCoin name by default to preserve backwards compatibility with existing wallets. Use MastiffCoin.conf by default and a datadir of MastiffCoin to keep backwards compatibility, but you can specify your own datadir and conf filename using commandline options if needed.
This worked perfect! One quick question, should it be setup stake=0, stake=1 or no stake in the .conf? I haven't dealt with this too much before but I want to make sure it syncs.

If you want to stake, you don't need anything in the conf file. If you want to disable staking, you would use staking=0 and/or set reservebalance=999999999

We already fixed the source on Github for both the MastiffCoin and MastCoin repositories, so if you're building from there you should be good to go - no conf file needed. We'll release a new Windows build as soon as possible, and the updated Mac wallet is expected to be released tomorrow.
member
Activity: 111
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.
Well I'm running an Amazon EC2 instance which will not connect. The wallet has been allowed in the firewall. My Windows 8.1 machine is on a different IP and in no way affiliated with the EC2. Both will not connect, both have been allowed through firewall, and both have other coin wallets downloading and syncing as we speak. So it really seems as if there is something wrong. I am going to make a config now and see what happens. Would I name it Mast.conf or MastiffCoin.conf?

Hmm, I see what you're saying now. I installed a new MastCoin wallet onto a fresh directory and it wouldn't sync.

** EDIT: I know what the problem is.. the search/replace for rebranding MastiffCoin to MastCoin in the wallet must have removed the nodes - we'll fix that up and release an updated version soon, sorry for the trouble.

I created a MastiffCoin.conf file with the following nodes, and it sync'd right up though:

addnode=node1.mastiffcoin.com
addnode=node2.mastiffcoin.com
addnode=node3.mastiffcoin.com

We'll investigate why those nodes aren't being sync'd from automatically, because they're the built in seednodes and should work just fine.

To answer your second question, yes the datadir and conf file are under the MastiffCoin name by default to preserve backwards compatibility with existing wallets. Use MastiffCoin.conf by default and a datadir of MastiffCoin to keep backwards compatibility, but you can specify your own datadir and conf filename using commandline options if needed.
This worked perfect! One quick question, should it be setup stake=0, stake=1 or no stake in the .conf? I haven't dealt with this too much before but I want to make sure it syncs.
member
Activity: 98
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.
Well I'm running an Amazon EC2 instance which will not connect. The wallet has been allowed in the firewall. My Windows 8.1 machine is on a different IP and in no way affiliated with the EC2. Both will not connect, both have been allowed through firewall, and both have other coin wallets downloading and syncing as we speak. So it really seems as if there is something wrong. I am going to make a config now and see what happens. Would I name it Mast.conf or MastiffCoin.conf?

Hmm, I see what you're saying now. I installed a new MastCoin wallet onto a fresh directory and it wouldn't sync.

** EDIT: I know what the problem is.. the search/replace for rebranding MastiffCoin to MastCoin in the wallet must have removed the nodes - we'll fix that up and release an updated version soon, sorry for the trouble.

I created a MastiffCoin.conf file with the following nodes, and it sync'd right up though:

addnode=node1.mastiffcoin.com
addnode=node2.mastiffcoin.com
addnode=node3.mastiffcoin.com

We'll investigate why those nodes aren't being sync'd from automatically, because they're the built in seednodes and should work just fine.

To answer your second question, yes the datadir and conf file are under the MastiffCoin name by default to preserve backwards compatibility with existing wallets. Use MastiffCoin.conf by default and a datadir of MastiffCoin to keep backwards compatibility, but you can specify your own datadir and conf filename using commandline options if needed.
member
Activity: 111
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.
Well I'm running an Amazon EC2 instance which will not connect. The wallet has been allowed in the firewall. My Windows 8.1 machine is on a different IP and in no way affiliated with the EC2. Both will not connect, both have been allowed through firewall, and both have other coin wallets downloading and syncing as we speak. So it really seems as if there is something wrong. I am going to make a config now and see what happens. Would I name it Mast.conf or MastiffCoin.conf?
legendary
Activity: 1139
Merit: 1000
TRUSTplus Dev
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.

Im noticing Nodes Smurfing as well.  They are blocking new wallets from installing quickly.  Time to get out the Ban-hammer.
member
Activity: 98
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?

There are three seed nodes, which are all currently functional, that are built into the wallet. It seems like something must be something blocking your connection to them? There's no version incompatibility between the last version that you must have been running (v1.0.1) and the latest rebranded MastCoin wallet (v1.1.0), so there shouldn't be any issue with multiple versions on the network, etc.
full member
Activity: 230
Merit: 100
[
{
"addr" : "89.106.59.189:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403837914,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89420,
"banscore" : 0
},
{
"addr" : "78.108.54.193:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403837960,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89423,
"banscore" : 0
},
{
"addr" : "86.152.84.52:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403838584,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89449,
"banscore" : 0
},
{
"addr" : "5.81.18.207:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403839309,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89472,
"banscore" : 0
},
{
"addr" : "188.165.3.223:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403839728,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89485,
"banscore" : 0
},
{
"addr" : "81.105.192.121:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917039,
"conntime" : 1403840144,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89498,
"banscore" : 0
},
{
"addr" : "216.108.167.85:12151",
"services" : "00000001",
"lastsend" : 1403917181,
"lastrecv" : 1403917182,
"conntime" : 1403840783,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89527,
"banscore" : 0
},
{
"addr" : "173.192.30.91:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403840978,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89532,
"banscore" : 0
},
{
"addr" : "108.163.232.221:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403841509,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89545,
"banscore" : 0
},
{
"addr" : "66.68.138.128:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403847580,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89763,
"banscore" : 0
},
{
"addr" : "71.120.15.84:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403848030,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 89782,
"banscore" : 0
},
{
"addr" : "80.229.22.200:12151",
"services" : "00000001",
"lastsend" : 1403917183,
"lastrecv" : 1403917183,
"conntime" : 1403854979,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 90024,
"banscore" : 0
},
{
"addr" : "184.173.115.98:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403885837,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 91089,
"banscore" : 0
},
{
"addr" : "181.54.134.19:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403895591,
"version" : 60014,
"subver" : "/Satoshi:1.0.1/",
"inbound" : false,
"startingheight" : 91417,
"banscore" : 0
},
{
"addr" : "50.80.62.215:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403897414,
"version" : 60014,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"startingheight" : 91475,
"banscore" : 0
},
{
"addr" : "174.45.80.214:12151",
"services" : "00000001",
"lastsend" : 1403917182,
"lastrecv" : 1403917182,
"conntime" : 1403901548,
"version" : 60014,
"subver" : "/Satoshi:1.1.0/",
"inbound" : false,
"startingheight" : 91607,
"banscore" : 0
}
]
member
Activity: 111
Merit: 10
no problems with my wallet
Would you mind going into the console and doing a getpeerinfo ? I can then take the IP's and make a config possibly. Has anyone tried to install the wallet with a clean image and not just an install over the top of the old wallet install?
sr. member
Activity: 336
Merit: 250
no problems with my wallet
member
Activity: 111
Merit: 10
I too can confirm that I have tried to install the wallet on 2 different OS and the wallet won't sync. It cannot find any active connections. Tried on Win 8.1 Pro, and Win Server 2012 R2. Allowed the wallets through the firewall to no avail. I am not sure if the server thing will even work but it is just a project of mine. Any input or list of active connection to build a .conf file would be appreciated. I want to start staking again but I re-installed Windows on all of my machines so I have to set things up again.
legendary
Activity: 1988
Merit: 1000
Hi dev

can you tell in percent  %  where you are on the wallet development ?

thanks !
sr. member
Activity: 336
Merit: 250
is everyone still voting on mintpal? we are all kind of hoping this coin explodes in popularity and volume and gets added to mintpal without a vote. but we should just keep at it anyway https://www.mintpal.com/voting#MAST
member
Activity: 98
Merit: 10
Wallet doesnt sync can i have a .conf file?

Could you have a firewall blocking it or something? The wallet should sync fine, there's no .conf file or addnodes needed.

You could try removing your peers.dat file to see if that helps.
full member
Activity: 182
Merit: 100
I don't know why you can't sync guys, my wallet is working perfectly and staking right now !

Some little changes on the website :

- New banner in "home"
- Updated link redirection to the CoinRecycler
- Added new windows wallet http://mastcoin.co/get-started
- Added new GITHUB Mastcoin
full member
Activity: 230
Merit: 100
I synced just fine, 16 active connections. Just run the qt without doing anything else.


Yes this coin is very much under the radar. Mentioned this coin to a person who is in cryptos on a different type of forum. He has a lot of Doge to recycle...hope he does it.
full member
Activity: 137
Merit: 100
Wallet doesnt sync can i have a .conf file?

same problem here, no active connections...
hero member
Activity: 518
Merit: 500
The blockchain is the future
Wallet doesnt sync can i have a .conf file?
sr. member
Activity: 336
Merit: 250
yea, i got a feeling this is going to be one of those coins that goes up all of a sudden, and people will be scratching there heads wondering how they missed it.

it's going under the radar because of the name. once it gets traction it's gonna be huge
full member
Activity: 646
Merit: 100
tozex.io
yea, i got a feeling this is going to be one of those coins that goes up all of a sudden, and people will be scratching there heads wondering how they missed it.
Pages:
Jump to: