Pages:
Author

Topic: [ANN] Fastcoin - FST - The Fastest coin so far in the market - is launched!! - page 19. (Read 238167 times)

fxj
newbie
Activity: 28
Merit: 0
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.
newbie
Activity: 9
Merit: 0
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.
full member
Activity: 364
Merit: 100
spattered throughout the golden ethers
Super responsive dev team and after 4 years in the making, they actually have a working product.

Long term holder now.
fxj
newbie
Activity: 28
Merit: 0
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.
legendary
Activity: 1080
Merit: 1055
DEV of DeepOnion community pool
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.
full member
Activity: 255
Merit: 102
uBlock.it Admin
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 Huh
What happened to Mainnet v1 Huh

Any dev care to chime in on this? Roll Eyes
newbie
Activity: 46
Merit: 0
https://scrypto.io/content/perma?id=1868

New breakout, maybe? Now we can surparse 1k sats, I think
fxj
newbie
Activity: 28
Merit: 0
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...
member
Activity: 82
Merit: 10
The Tao of Crypto
That's a great domain name!
member
Activity: 81
Merit: 10
dev,

the coin be on bittrex ?

They did apply for listing on all main Xchangers, posted here several times.
newbie
Activity: 16
Merit: 0
Looks good, i see the redirect is working already. Thank you!!
member
Activity: 99
Merit: 10
dev,

the coin be on bittrex ?
newbie
Activity: 35
Merit: 0
*Breaking*

some great news, I have acquired Fastcoin.Org and will be developing it as a community site dedicated to Fastcoin
It will be an additional site to the one the devs run at Fastcoin.ca

For the immediate short term I have redirected it to .ca site so we gain some type in traffic and new users who may visit it in the hope the site is there.

This is quite a coup as if you check there is a lot of competiton for the fastcoin domains due to several coin dealers and other businesses using the name

imho this is the single best domain for any crypto to own, as on the org, it was actually originally registered long before bitcoin.org! due to compettion for the name
ALL extensions of any note are taken .info, .co, .com, .us the lot

even all the fastcoins plural main domains are gone!

I was watching the domain become expired couple years back but someone won at auction and then was reregistered. I now have it in my possession and fear not will never let expire

it is the domain extension any credible crypto is expected to own, the .org, litecoin, bitcoin etc

I will develop the domain as explained in time and will include blog, info, how to guides, merchant lists, possible bounty page and I have some very big plans for some other stuff much in fst favour which wont mention yet  Cool

If at any point in future i am unable to keep development up etc I will transfer to devs, but feel very healthy for us as a community to own this as well as a backup site to the .ca

the .ca site is great of course and will always be the 'main site' as devs, however .ca is country specific domain so will not rank as high as .com etc
plus as said we have lots of competition for name so another site to take top rankings on main search engines can help massively

plus I hope my site will greatly help traffic to .ca and twitter and our crypto and community
it also stops it going back to cyber squatters and possibly a fake site

so, this is great news
no timeline on site yet, but hope to get cracking in say a month or so

as a tandem site it will allow us to possibly crowdfund new developments and promote fastcoin and take our crypto forward as bitcoin did, the bitcoin community after all lost their developer, satoshi and bitcoin.org was very static but they developed their own sites, graphics, ideas, forums and so on, we have so much going for us
will be great to see all the new stuff the fastcoin devs are doing and we can actively move us forward in tandem with our new site

all hail Guido! lol
Fantastic, thank you!  Your time, experience and expense is very appreciated!
full member
Activity: 255
Merit: 102
uBlock.it Admin
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 Huh
What happened to Mainnet v1 Huh
full member
Activity: 255
Merit: 102
uBlock.it Admin
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
newbie
Activity: 21
Merit: 0
Today after loading the wallet, it stopped synchronizing. There are 12 active connections, but the source of the blocks is unavailable
http://s018.radikal.ru/i505/1707/76/bb0ecdf1f6ca.png
Thank you again for your patience everyone as our support team continues to investigate this issue.

We would like to thank community member "CryptoSecure" for his contribution and providing a "work around fix" for users who are experiencing the above reported syncing issue.

Please refer to the following link below for more details.

http://www.fastcointalk.org/index.php/topic,1124.0.html

Best

Fast
Thank you Fast-coin for your post!

The attached document helped me, keep up the great work, you guy's are the best!

Edith
full member
Activity: 163
Merit: 100
Fast and secure crypto currency of the future
Today after loading the wallet, it stopped synchronizing. There are 12 active connections, but the source of the blocks is unavailable

Thank you again for your patience everyone as our support team continues to investigate this issue.

We would like to thank community member "CryptoSecure" for his contribution and providing a "work around fix" for users who are experiencing the above reported syncing issue.

Please refer to the following link below for more details.

http://www.fastcointalk.org/index.php/topic,1124.0.html

Best

Fast
member
Activity: 99
Merit: 10
hey,
i support on you coin but many people not know this coin at all
i think we need to do campign on twitter

They have a twitter account up and running. It's @fast_coin
i think its not enough
also it need in more exchange
member
Activity: 116
Merit: 10
Quack.
so - whats that syncing problem about?
newbie
Activity: 25
Merit: 0
hey,
i support on you coin but many people not know this coin at all
i think we need to do campign on twitter

They have a twitter account up and running. It's @fast_coin
Pages:
Jump to: