[ANN] Fastcoin - FST - The Fastest coin so far in the market - is launched!!

[matan]

dev,

the coin be on bittrex ?

[fastcoin-ok]

dev,

the coin be on bittrex ?

They did apply for listing on all main Xchangers, posted here several times.

[fxj]

It appears that many nodes on the network are not up to date or have forked off, I think this may be due to some clients connecting to the wrong network (not fastcoin) for whatever reason.
If you're stuck on block 10175412 you may need to re-index or revert back to the latest chainstate from google drive before trying the following.

I have found the following nodes to be reliable and fully synced.

addnode=217.77.220.34
addnode=207.210.56.43
addnode=85.25.197.148:3344
addnode=71.252.137.242
addnode=71.252.137.246


For anyone still having issues getting synced try using the following parameters in your conf file.

connect=217.77.220.34
connect=207.210.56.43
connect=85.25.197.148:3344
connect=71.252.137.242
connect=71.252.137.246
listen=1

After you're synced you should be able to safely change back to addnode= but if you're daemon ends up establishing an outbound connection to a bad node you may end up having to re-index.
The connect= parameter prevents your node from establishing additional outbound connections beyond what you specified, which can be helpful if you have a set of reliable/trusted nodes.

cheers

ziiip, thanks for the suggestion. I have only checked my Mac clients so far.

- I haven't been able to edit peers.dat, so not able to use the connect command so far
- I added the hosts via console instead (example: addnode 217.77.220.34 add), and they showed up as active in my client list, but still no sync

Won't downgrade to the old version yet, unless I really need to...

[ribdyne]

https://scrypto.io/content/perma?id=1868

New breakout, maybe? Now we can surparse 1k sats, I think

[ziiip]

I am still very curious about block 2990306

I noticed something on m0gliE's branch

https://gitlab.com/m0gliE/litecoin/blob/exp-0.10-mark2/src/chainparams.cpp#L175

Code:

@@ 175       // Fastcoin: Mainnet v2 enforced as of block 710k
@@ 176          nEnforceV2AfterHeight = 2990306;

What is Mainnet v2
What happened to Mainnet v1

Any dev care to chime in on this?

[youngwebs]

ziiip, thanks for the suggestion. I have only checked my Mac clients so far.

- I haven't been able to edit peers.dat, so not able to use the connect command so far
- I added the hosts via console instead (example: addnode 217.77.220.34 add), and they showed up as active in my client list, but still no sync

Won't downgrade to the old version yet, unless I really need to...

You should not edit your peers.dat, but fastcoin.conf instead. The fastcoin.conf file is the file you can addnode=*.*.*.* lines to. Once you have done this restart the client and it should start syncing.

[fxj]

You should not edit your peers.dat, but fastcoin.conf instead. The fastcoin.conf file is the file you can addnode=*.*.*.* lines to. Once you have done this restart the client and it should start syncing.

Thanks for your input youngweb.

I couldn't find the fastcoin.conf file where I expected it, ~/Library/Application Support/Fastcoin

And as console won't take the connect command, I had to settle for addnode instead. The clients were added though, and showed up as active peers, so if pointing to these nodes would suffice, that should have made it.

Anyway, I read up on the qt documentation, as it turns out (and as I had forgotten) the *.conf file is not created automatically --> I created it manually and placed it in the folder. I used the connect command instead of addnode here, as the connect command supposedly makes the client connect to only the nodes that I specify, at least initially. Firing up the fst client, it connected to the nodes that I had listed, and it now says that it is synchronising, however still stuck on block 10175412.

On a sidenote - several of the clients listed by ziiip was now running the older version. I took them out of the list, now only ver 10 nodes, still no change though. Also took out a ver 10 client that didn't seem to be updated to the latest blocks.

Current ver 10 nodes:

217.77.220.34 confirmed up-to-date syncwise
71.252.137.246 confirmed up-to-date syncwise

If anyone knows of more confirmed ver 10 nodes that are up-to-date, please add to this list here.

[zecon]

Super responsive dev team and after 4 years in the making, they actually have a working product.

Long term holder now.

[bigdaddy1000]

I have two wallets, one on a pc and one on a desktop. Both are stuck at 6 days behind. I have 12 active connections. One wallet is empty, but the other has most of my fastcoin. Can I reinstall the wallet with my fastcoins? Any advice would be greatly appreciated.

Note: Both wallets were previously working and had been for a couple of months.

[fxj]

I have two wallets, one on a pc and one on a desktop. Both are stuck at 6 days behind. I have 12 active connections. One wallet is empty, but the other has most of my fastcoin. Can I reinstall the wallet with my fastcoins? Any advice would be greatly appreciated.

Note: Both wallets were previously working and had been for a couple of months.

bigdaddy1000, see post 1711 and forward, last page and this page.

So far:

- one workaround by going back to older version of the client
- another workaround trying to connect to version 10 clients only

Dev team is on it, looking for the precise reason for this issue, as well as a permanent fix.

[MarauderV]

Can anyone tell me the features they announced on the roadmap ?
I'm at work and can't watch the video on youtube.

[fastcoin-ok]

Can anyone tell me the features they announced on the roadmap ?
I'm at work and can't watch the video on youtube.

Mani point I see is the Android/IPHONE wallet available in september on Google Play. Most of crypto don't have it.

[CoffeeClone]

just unbelievable... Fast wars...

https://www.youtube.com/watch?v=ApQ6w38Avh0

[bigdaddy1000]

I have two wallets, one on a pc and one on a desktop. Both are stuck at 6 days behind. I have 12 active connections. One wallet is empty, but the other has most of my fastcoin. Can I reinstall the wallet with my fastcoins? Any advice would be greatly appreciated.

Note: Both wallets were previously working and had been for a couple of months.

bigdaddy1000, see post 1711 and forward, last page and this page.

So far:

- one workaround by going back to older version of the client
- another workaround trying to connect to version 10 clients only

Dev team is on it, looking for the precise reason for this issue, as well as a permanent fix.

thanks fxj,

can I go back to the older client without having any issues losing any of the fastcoin that I have in that wallet? And for the second, how would I connect to version 10 clients only?

Thanks in advance!

[fxj]

thanks fxj,

can I go back to the older client without having any issues losing any of the fastcoin that I have in that wallet? And for the second, how would I connect to version 10 clients only?

Thanks in advance!

bigdaddy1000,

- if you do it right (especially: first of all backup the wallet, and keep that backup in a good place), you will not lose any coins. More info here, as per fast-coin's post #1721 http://www.fastcointalk.org/index.php/topic,1124.0.html

- in order to connect to version 10 hosts only, you could alter the fastcoin.conf file (or add it if it's not in place yet, it's not a mandatory file), by adding version 10 hosts using the connect command, and adding "listen=1" since this is required when using the connect command. See ziiip's post #1723 for more details. One issue with this approach is of course to find version 10 clients, and version 10 clients that are up-to-date at that. I found a couple of the ones provided by ziiip to look ok (see my post #1731), but I still couldn't get my client to sync even though it connected to those version 10 hosts, so not sure whether this is a way forward at all.

[fast-coin]

I am still very curious about block 2990306

I noticed something on m0gliE's branch

https://gitlab.com/m0gliE/litecoin/blob/exp-0.10-mark2/src/chainparams.cpp#L175

Code:

@@ 175       // Fastcoin: Mainnet v2 enforced as of block 710k
@@ 176          nEnforceV2AfterHeight = 2990306;

What is Mainnet v2
What happened to Mainnet v1

Any dev care to chime in on this?

Thank you Ziiip,

That's a good find, and am glad to see some curious developers taking the time to look 😉

That simply was a marker to let all clients below 8.5.3 to no longer participate and broadcast on the FastCoin network once this block height has been reached.  

Being that our coin has been in over 4 years of existence, we have had several wallet version releases and wallets from 8.5.3 and up are still fully supported.

Thanks again for pointing this out, hope this answers your question.

Best
Fast

[fast-coin]

ziiip, thanks for the suggestion. I have only checked my Mac clients so far.

- I haven't been able to edit peers.dat, so not able to use the connect command so far
- I added the hosts via console instead (example: addnode 217.77.220.34 add), and they showed up as active in my client list, but still no sync

Won't downgrade to the old version yet, unless I really need to...

You should not edit your peers.dat, but fastcoin.conf instead. The fastcoin.conf file is the file you can addnode=*.*.*.* lines to. Once you have done this restart the client and it should start syncing.

Thank you Youngwebs,

We appreciate your assistance on this to our community members as the lead Dev's and I have been inidated with many requests at the moment.  If you have not already done so, please feel free to join our forum at www.fastcointalk.org and add any addtional relavant supporting information into a thread their, as it may further assist users with additional examples etc.  Please DM myself or Cheetahx if you would like your status elevated at fastcointalk.org, this will give you additional tools you can use to futher assist community members.

Best
Fast

[Cheetahx]

Super responsive dev team and after 4 years in the making, they actually have a working product.

Long term holder now.

Thank you Zecon!

Although we do not feel worthy of it yet, we certainly much appreciate the praise ;-)

Looks like our Crypto Wars campaign has been an smashing success!  It also looks like the video may have caught mainstream media attention as well!  We will wait and see if it goes viral, but for now Fastcoin Foundation members and myself are doing our best to keep up with the flood of emails hitting our inbox.  We expect to be posting some additional significant announcements in the weeks ahead, thank you all for your continued support!



For those of you who have not seen the video, you can watch it here.  We have updated the version to "Editors Cut" with reduced background noise and improved audio.  It helps clicking on it a few times if you would like to see it go viral, also please feel free to share with your family and friends as 99.99% of the public still do not have a CLUE about what BITCOIN is let alone FastCoin!

https://youtu.be/GNzu3gWBXKU

Sincerely

/C

[ziiip]

I am still very curious about block 2990306

I noticed something on m0gliE's branch

https://gitlab.com/m0gliE/litecoin/blob/exp-0.10-mark2/src/chainparams.cpp#L175

Code:

@@ 175       // Fastcoin: Mainnet v2 enforced as of block 710k
@@ 176          nEnforceV2AfterHeight = 2990306;

What is Mainnet v2
What happened to Mainnet v1

Any dev care to chime in on this?

Thank you Ziiip,

That's a good find, and am glad to see some curious developers taking the time to look 😉

That simply was a marker to let all clients below 8.5.3 to no longer participate and broadcast on the FastCoin network once this block height has been reached.  

Being that our coin has been in over 4 years of existence, we have had several wallet version releases and wallets from 8.5.3 and up are still fully supported.

Thanks again for pointing this out, hope this answers your question.

Best
Fast

So it's just a coincidence that all 10.2 nodes get stuck on block 2990306?

The chainparams for 10.2.2-irc specify v2 at block=1 see the following

https://github.com/fastcoinproject/fastcoin/blob/10.2.2-irc/src/chainparams.cpp#L181

And 10.2.2 specifies block=5500000 while m0gliE's branch specifies block=2990306

https://github.com/fastcoinproject/fastcoin/blob/10.2.2/src/chainparams.cpp#L181

Which branch was the windows binary on sourceforge compiled from
And which chainparams.cpp is correct?

[dan_and_shan]

thanks fxj,

can I go back to the older client without having any issues losing any of the fastcoin that I have in that wallet? And for the second, how would I connect to version 10 clients only?

Thanks in advance!

bigdaddy1000,

- if you do it right (especially: first of all backup the wallet, and keep that backup in a good place), you will not lose any coins. More info here, as per fast-coin's post #1721 http://www.fastcointalk.org/index.php/topic,1124.0.html

- in order to connect to version 10 hosts only, you could alter the fastcoin.conf file (or add it if it's not in place yet, it's not a mandatory file), by adding version 10 hosts using the connect command, and adding "listen=1" since this is required when using the connect command. See ziiip's post #1723 for more details. One issue with this approach is of course to find version 10 clients, and version 10 clients that are up-to-date at that. I found a couple of the ones provided by ziiip to look ok (see my post #1731), but I still couldn't get my client to sync even though it connected to those version 10 hosts, so not sure whether this is a way forward at all.

Any other work around, started fresh install with new config ( even with this config it was still connecting to older clients), it said synced up to 4 days ago, when i checked back, it was back at 8 days behind, and no block source found.

UpdateTip: new best=3e670a2aae4bd78c5c1791126c45daaa627b1965a2bb7b33417cdbe84bff64d6  height=10175411  log2_work=58.10868  tx=12384241  date=2017-07-25 19:31:15 progress=0.994393  cache=56489
2017-08-02 23:56:27 UpdateTip: new best=d8f407dbbebe3b8a7a6c3ea779a85f957df96d2df25b40d42e63cae70bb269c1  height=10175412  log2_work=58.120519  tx=12384242  date=2017-07-25 19:31:15 progress=0.994393  cache=56490
2017-08-02 23:58:22 ERROR: AcceptToMemoryPool : nonstandard transaction: version
2017-08-03 00:00:22 ERROR: AcceptToMemoryPool : nonstandard transaction: version
2017-08-03 00:01:37 opencon thread interrupt
2017-08-03 00:01:37 irc thread exit
2017-08-03 00:01:37 msghand thread interrupt
2017-08-03 00:01:37 addcon thread interrupt
2017-08-03 00:01:37 dumpaddr thread stop
2017-08-03 00:01:37 net thread interrupt
2017-08-03 00:01:37 Shutdown: In progress...
2017-08-03 00:01:37 StopNode()
2017-08-03 00:01:37 UPNP_DeletePortMapping() returned : 403
2017-08-03 00:01:37 upnp thread interrupt