[ANN] FedoraCoin (TiPS) - New Dev team: Fedoracoin Foundation

[psycodad]

If no updates on the source are being made I think we should consider this coin dead.
It is compromised, and it's not going to be better with more nodes.

1 thing might help...
If the price at least triples in value, so more hashrate can be pointed on a good profitability, makes it much harder to achieve >51%...

But at the end.. On this stage the price will only drop, making the problem even bigger..

I'm not sure that this has anything with 51% attack, because as I said before, I have the blocks confirmed on the pool, sent to Bter, so around 150 confirmations, even more, and then someone has changed complete network with his own blocks, new created, 51% attack gives you Orphan in that moment, but this is not the case here !!
As you can see I still have Pending blocks on Bter but that txs doesn't exist anymore !!! so this blocks will be never confirmed

Did you also onsider selfish mining with a hidden chain, releasing blocks when needed?
You don't need 51% for this, 25-35% are enough and it annoys the hell out of honest miners.

I bet that's what we see here.

[1715072017]

1715072017

[1715072017]

1715072017

[plast555]

but how that person implement hidden chain into the regular chain ?
how is that even possible ?
so, let's fight fire with fire !?
Seems that what Verge done with multiple algorithms succeed ! maybe that is the answer !?

[RNOVAKOSKY]

Hello ppl

After broked chain, exchange on cryptopia stoped to work last week. And since yesterday isn't more disponible to exchange, only to transfer. Any notices about?

[nemgun]

Hello guys, i hope this log will help you to help me solve my problem

2016-06-16 22:14:25 FedoraCoin version v1.1.0.0-g80bd0e3-beta (Mon, 31 Mar 2014 23:55:36 +0200)
2016-06-16 22:14:25 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014
2016-06-16 22:14:25 Default data directory C:\Users\BleMed\AppData\Roaming\FedoraCoin
2016-06-16 22:14:25 Using data directory C:\Users\BleMed\AppData\Roaming\FedoraCoin
2016-06-16 22:14:25 Using at most 125 connections (2048 file descriptors available)
2016-06-16 22:14:25 Using 8 threads for script verification
2016-06-16 22:14:25 init message: Vérification du porte-monnaie...
2016-06-16 22:14:25 dbenv.open LogDir=C:\Users\BleMed\AppData\Roaming\FedoraCoin\database ErrorFile=C:\Users\BleMed\AppData\Roaming\FedoraCoin\db.log
2016-06-16 22:14:25 Bound to [::]:44889
2016-06-16 22:14:25 Bound to 0.0.0.0:44889
2016-06-16 22:14:25 init message: Chargement de l’index des blocs…
2016-06-16 22:14:25 Opening LevelDB in C:\Users\BleMed\AppData\Roaming\FedoraCoin\blocks\index
2016-06-16 22:14:25 Opened LevelDB successfully
2016-06-16 22:14:25 Opening LevelDB in C:\Users\BleMed\AppData\Roaming\FedoraCoin\users
2016-06-16 22:14:25 Opened LevelDB successfully
2016-06-16 22:14:25 Opening LevelDB in C:\Users\BleMed\AppData\Roaming\FedoraCoin\chainstate
2016-06-16 22:14:25 Opened LevelDB successfully
2016-06-16 22:14:25 LoadBlockIndexDB(): last block file = 0
2016-06-16 22:14:25 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=1, size=378, heights=0...0, time=2013-12-21...2013-12-21)
2016-06-16 22:14:25 LoadBlockIndexDB(): transaction index disabled
2016-06-16 22:14:25 LoadBlockIndexDB(): hashBestChain=746b18d1b206b817408c355a256a144e740579b6729043d184574642077f2054  height=0 date=2013-12-21 22:47:52
2016-06-16 22:14:25 init message: Vérification des blocs...
2016-06-16 22:14:25  block index              30ms
2016-06-16 22:14:25 init message: Chargement du porte-monnaie…
2016-06-16 22:14:25 nFileVersion = 1010000
2016-06-16 22:14:25  wallet                    5ms
2016-06-16 22:14:25 init message: Chargement des adresses…
2016-06-16 22:14:25 Loaded 1 addresses from peers.dat  0ms
2016-06-16 22:14:25 mapBlockIndex.size() = 1
2016-06-16 22:14:25 nBestHeight = 0
2016-06-16 22:14:25 setKeyPool.size() = 100
2016-06-16 22:14:25 mapWallet.size() = 0
2016-06-16 22:14:25 mapAddressBook.size() = 1
2016-06-16 22:14:25 AddLocal([2001:0:9d38:90d7:3cbf:cce:969a:85bf]:44889,1)
2016-06-16 22:14:25 dnsseed thread start
2016-06-16 22:14:25 upnp thread start
2016-06-16 22:14:25 net thread start
2016-06-16 22:14:25 addcon thread start
2016-06-16 22:14:25 opencon thread start
2016-06-16 22:14:25 msghand thread start
2016-06-16 22:14:25 dumpaddr thread start
2016-06-16 22:14:25 Loading addresses from DNS seeds (could take a while)
2016-06-16 22:14:25 1 addresses found from DNS seeds
2016-06-16 22:14:25 dnsseed thread exit
2016-06-16 22:14:25 init message: Chargement terminé
2016-06-16 22:14:25 refreshWallet
2016-06-16 22:14:26 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:30 connection timeout
2016-06-16 22:14:30 ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
2016-06-16 22:14:31 socket closed
2016-06-16 22:14:31 connection timeout
2016-06-16 22:14:31 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:31 No valid UPnP IGDs found
2016-06-16 22:14:31 upnp thread exit
2016-06-16 22:14:36 connection timeout
2016-06-16 22:14:37 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:42 connection timeout
2016-06-16 22:14:42 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:47 connection timeout
2016-06-16 22:14:48 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:53 connection timeout
2016-06-16 22:14:53 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:14:58 connection timeout
2016-06-16 22:14:59 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:15:04 connection timeout
2016-06-16 22:15:04 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:15:09 connection timeout
2016-06-16 22:15:10 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:15:15 connection timeout
2016-06-16 22:15:15 trying connection 5.39.99.51:44889 lastseen=91.7hrs
2016-06-16 22:15:20 connection timeout
2016-06-16 22:15:21 trying connection 5.39.99.51:44889 lastseen=91.7hrs

[EpyxZ]

Is this coin under suspicion of dev scam or chain manipulation? just curious. do not want to invest if so.

Thank You

[nemgun]

no node working

[EpyxZ]

no node working

KK thanks for the very quick answer Good to know. TY

[nemgun]

here is a list of working nodes
addnode=101.201.44.98
addnode=103.253.43.162
addnode=113.233.96.55
addnode=117.140.166.87
addnode=119.119.37.85
addnode=121.41.6.161
addnode=123.77.106.246
addnode=128.199.148.87
addnode=139.196.230.81
addnode=144.76.90.209
addnode=146.185.143.228
addnode=148.251.19.213
addnode=154.98.193.149
addnode=159.203.5.8
addnode=162.243.210.240
addnode=162.255.117.105
addnode=172.93.110.218
addnode=174.78.200.194
addnode=175.15.206.173
addnode=175.164.171.215
addnode=175.167.152.159
addnode=178.140.25.85
addnode=178.62.72.53
addnode=180.241.146.191
addnode=182.107.8.219
addnode=188.166.165.61
addnode=188.166.181.68
addnode=189.55.59.230
addnode=192.99.13.67
addnode=192.99.241.164
addnode=192.99.62.23
addnode=192.99.8.126
addnode=205.251.171.139
addnode=212.65.7.40
addnode=221.200.50.85
addnode=222.74.77.122
addnode=24.125.85.28
addnode=36.79.136.211
addnode=41.241.111.218
addnode=46.101.131.172
addnode=46.254.11.158
addnode=5.135.108.204
addnode=5.86.98.165
addnode=68.101.63.60
addnode=68.96.236.163
addnode=75.137.110.60
addnode=76.170.13.90
addnode=78.70.227.24
addnode=81.218.0.98
addnode=82.196.3.108
addnode=83.234.245.201
addnode=84.107.174.140
addnode=87.195.238.234
addnode=90.32.33.122
addnode=91.134.233.254
addnode=96.87.169.209
addnode=98.115.147.74
addnode=99.90.152.71

[EpyxZ]

here is a list of working nodes
addnode=101.201.44.98
addnode=103.253.43.162
addnode=113.233.96.55
addnode=117.140.166.87
addnode=119.119.37.85
addnode=121.41.6.161
addnode=123.77.106.246
addnode=128.199.148.87
addnode=139.196.230.81
addnode=144.76.90.209
addnode=146.185.143.228
addnode=148.251.19.213
addnode=154.98.193.149
addnode=159.203.5.8
addnode=162.243.210.240
addnode=162.255.117.105
addnode=172.93.110.218
addnode=174.78.200.194
addnode=175.15.206.173
addnode=175.164.171.215
addnode=175.167.152.159
addnode=178.140.25.85
addnode=178.62.72.53
addnode=180.241.146.191
addnode=182.107.8.219
addnode=188.166.165.61
addnode=188.166.181.68
addnode=189.55.59.230
addnode=192.99.13.67
addnode=192.99.241.164
addnode=192.99.62.23
addnode=192.99.8.126
addnode=205.251.171.139
addnode=212.65.7.40
addnode=221.200.50.85
addnode=222.74.77.122
addnode=24.125.85.28
addnode=36.79.136.211
addnode=41.241.111.218
addnode=46.101.131.172
addnode=46.254.11.158
addnode=5.135.108.204
addnode=5.86.98.165
addnode=68.101.63.60
addnode=68.96.236.163
addnode=75.137.110.60
addnode=76.170.13.90
addnode=78.70.227.24
addnode=81.218.0.98
addnode=82.196.3.108
addnode=83.234.245.201
addnode=84.107.174.140
addnode=87.195.238.234
addnode=90.32.33.122
addnode=91.134.233.254
addnode=96.87.169.209
addnode=98.115.147.74
addnode=99.90.152.71

wow. Lots of nodes there. was there a req for hosting node?

[nemgun]

i took them from the blockchain, but it seems that only two peers are working:

188.166.181.68:44889
75.137.110.60:44889

[psycodad]

but how that person implement hidden chain into the regular chain ?
how is that even possible ?
so, let's fight fire with fire !?
Seems that what Verge done with multiple algorithms succeed ! maybe that is the answer !?

I have linked a few articles above that explain selfish mining, but lets have a short example:

Say Alice, Bob and Carol are honest miners, they currently all mine on block X.

Mallory is a malicious selfish miner and she disconnects her two nodes from the network (i.e. by firewalling them from other nodes).
Now Mallory also starts to mine on block X, but if Mallory finds a block, she won't let the network know, instead she watches the block-explorer to see if one of Alice, Bob or Carol finds a block.

Assume Mallory has some powerful miners rented and has already advanced to block X+8, now if she sees that Bob found block X, she opens her firewalling and just releases her block X and her block X+1 to the network. Bobs block X will be orphaned and Bob, Alice and Carol have to restart mining on Mallory's block X+2 (Bob, Alice and Carole are wasting their mining power now, since the Mallory is already at X+8, in the meantime she advance to maybe X+10).

Now Carole finds block X+3 and shortly after Mallory releases her blocks X+3 and X+4, again Carols block is orphaned and Bob, Carol and Alice have to restart mining on block X+5 (which Mallory has since some time already).

Naturally the same principle works for X+100 or X+1000 if Mallory has advanced her private chain far enough.

We do not see this often in coins, because a coin that is attacked this way is loosing in value and that normally hurts the attacker. However if the attacker has not the goal of getting a financial benefit, he can kill a coin like this with ~25-35% of total hash power and I bet this is what we see here again.

Note that in practice you probably have a patched wallet so you can release single blocks at your will anytime you want. With just firewalling your nodes you can just release your whole private chain at once and not blockwise.

Standard disclaimer: I am noob and I might have not the slightest clue what I am talking about and you all should do your own research before basing any decision on what I say, I am just voicing my oppinion.

[plast555]

but how that person implement hidden chain into the regular chain ?
how is that even possible ?
so, let's fight fire with fire !?
Seems that what Verge done with multiple algorithms succeed ! maybe that is the answer !?

I have linked a few articles above that explain selfish mining, but lets have a short example:

Say Alice, Bob and Carol are honest miners, they currently all mine on block X.

Mallory is a malicious selfish miner and she disconnects her two nodes from the network (i.e. by firewalling them from other nodes).
Now Mallory also starts to mine on block X, but if Mallory finds a block, she won't let the network know, instead she watches the block-explorer to see if one of Alice, Bob or Carol finds a block.

Assume Mallory has some powerful miners rented and has already advanced to block X+8, now if she sees that Bob found block X, she opens her firewalling and just releases her block X and her block X+1 to the network. Bobs block X will be orphaned and Bob, Alice and Carol have to restart mining on Mallory's block X+2 (Bob, Alice and Carole are wasting their mining power now, since the Mallory is already at X+8, in the meantime she advance to maybe X+10).

Now Carole finds block X+3 and shortly after Mallory releases her blocks X+3 and X+4, again Carols block is orphaned and Bob, Carol and Alice have to restart mining on block X+5 (which Mallory has since some time already).

Naturally the same principle works for X+100 or X+1000 if Mallory has advanced her private chain far enough.

We do not see this often in coins, because a coin that is attacked this way is loosing in value and that normally hurts the attacker. However if the attacker has not the goal of getting a financial benefit, he can kill a coin like this with ~25-35% of total hash power and I bet this is what we see here again.

Note that in practice you probably have a patched wallet so you can release single blocks at your will anytime you want. With just firewalling your nodes you can just release your whole private chain at once and not blockwise.

Standard disclaimer: I am noob and I might have not the slightest clue what I am talking about and you all should do your own research before basing any decision on what I say, I am just voicing my oppinion.

yes I was reading a lot that what you linked and this what you are saying make sense a lot !!
Thank you !!
But really, how to fight with this ? Or we need some very active Dev, who will make Hard Fork everytime when that happened so the attacker will quit at the end or, as I said before, as Verge, multialgorithm or make POW/POS.
Didn't know that you can mining anything when you are disconnected from the network, but people learn while they are alive...really sad, I'm mining this coin months and months, if you ask me, the best mining coin ever !!

[psycodad]

Didn't know that you can mining anything when you are disconnected from the network, but people learning while they alive...really sad, I'm mining this coin months and months, if you ask me, the best mining coin ever !!

If you run two nodes, for your two nodes you are not disconnected - your are the network in your own nodes view! Every wallet I've seen needs two nodes at least before it starts accepting blocks. By isolating your nodes you simulate a natural fork that happens when networks divide due to failures or outages in links etc.

[plast555]

Didn't know that you can mining anything when you are disconnected from the network, but people learning while they alive...really sad, I'm mining this coin months and months, if you ask me, the best mining coin ever !!

If you run two nodes, for your two nodes you are not disconnected - your are the network in your own nodes view! Every wallet I've seen needs two nodes at least before it starts accepting blocks. By isolating your nodes you simulate a natural fork that happens when networks divide due to failures or outages in links etc.

yeah just teach me lool
for few days you will have one more attacker ... just kidding

[myc066]

One miner monopolize tips mining,If other miners(pools) find block,He will 51% attack, Then the block will change to orphan,Bter know the miner,I think bter let he do!This is why bter no tips lost .

[myc066]

One miner monopolize tips mining,If other miners(pools) find block,He will 51% attack, Then the block will change to orphan,Bter know the miner,I think bter let he do!This is why bter no tips lost .the bter doposit address ,EXv7WRqupUvgX1oGxHck7Uu2kGmnPNYrhP,The miner deposite tip 13 May.
Block  1282898 ,I think we  must prevent the attacker immediately,Fork from block 12900000,It is  hard to find DEV,But let tips blockchain explorer shop stop in 12900000,wait wallet updat,It will useful for tips.

[Cryptoid]

Could 2 different but compatible wallets be causing "some" of the issues we've been having with forks:



Correct me if I'm wrong, but we should NOT be running the 2.0 wallet from March of this year (2016).  
This 2.0 wallet is from (https://fedoracoin_site/) the SHA256 takeover group...

We need to clear the air and root out some "posers" posting on this forum who are giving misleading information.

At this point, there are only 2 I trust, psycodad and testbug.  There may be others who haven't posted for awhile.
Maybe I'm missing something here, if so, please correct me.

[RJF19]

Could 2 different but compatible wallets be causing "some" of the issues we've been having with forks:



Correct me if I'm wrong, but we should NOT be running the 2.0 wallet from March of this year (2016).  
This 2.0 wallet is from (https://fedoracoin_site/) the SHA256 takeover group...

We need to clear the air and root out some "posers" posting on this forum who are giving misleading information.

At this point, there are only 2 I trust, psycodad and testbug.  There may be others who haven't posted for awhile.
Maybe I'm missing something here, if so, please correct me.

I believe thats possible but, I'm no expert. I can say however that I'm using the "v1.1.0.0-g80bd0e3-beta" wallet without problems for some time now. Until this gets sorted out, no one should be installing or using any newer releases. (my opinion)

EDIT: Just opened my wallet, the version listed above, which hasn't been opened for a while and synced up within 10 minutes showing 13 active connections. No problems here, still holding 400 M.

[plast555]

The only question and problem is why this person who are robbing the network after 10 days still doing that.
So why Dev still didn't stopped him ? and why Bter still accepting his stolen coins ?

[Cryptoid]

The only question and problem is why this person who are robbing the network after 10 days still doing that.
So why Dev still didn't stopped him ? and why Bter still accepting his stolen coins ?

There is NO dev per say, only 1) original team and 2) some individuals attempting to take over the coin for their own purposes.  Only "someone" with an "altered" wallet and some serious hash power could be disrupting the chain like has been happening.  Any names come to mind???

Anyone who has any interest in keeping this coin from being taken over by a single entity, and we all know who that is, should only be using the official 1.1.0.0 wallet.  I also suggest we rely less on the "larger" exchange and use the smaller exchanges.

P.S. To get things started, I'll pledge 1,000,000 TiPS and 2 LTC to the original "dev" team for programmer(s) who contribute to a real wallet update that includes some features that strengthen the security of the coin.  Psychodad, give me a wallet address(s), and I'll deposit them today. (to be returned if the wallet isn't updated     )