Topic: [ANN] FedoraCoin (TiPS) - New Dev team: Fedoracoin Foundation - page 73. (Read 111289 times)

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.

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

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

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

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

no node working

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

Thank You

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

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?

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 !?

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.

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

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..

hey dev what's are you doing to slove this problem?
i investigate 2 chain to check my txid and all my slove block status confirmed in http://www.fedoracoin.xyz:3001/tx/3f5de3decdd410c9d912cdfae60154f9c6c4eaa56f3573706bc562441e4fb687
In other chain lost (ORPHAN) and not listed like in https://chainz.cryptoid.info
I think dev must be close 1 chain and prioritation with 1 chain like http://www.fedoracoin.xyz:3001 just keep chain live..

I don't think that is what you say the problem.
1. a lot of coins has just few nodes and never happened nothing similar
2. I'm mining on Smarterhash with high hashrate, then how so that I personally never hack the network on that way as you said ?
3. to me seams that someone who have an access like dev, messing up with the chain creating the new blocks, and as you can see if you follow the network, that person let 20 - 50 blocks, then cut them out and past his blocks with multiple new created addresses and then again and again.... and the same person manipulating the price on Bter because if you following Tips, you can see how someone, pump dump than again pump the price in just few minutes, so it's obvious that this is just one person, in normal world this would be the case for the jail sentence, but sad thing is that in crypto people can still doing this
4. wooow, what I just found, even confirmed blocks from yesterday what was sent to Bter, later was deleted from network !!!!

We need new Dev who will stand up for the people ! Not someone who is hiding behind the problems, not communicating, being so suspicious... 

Hi Plast555 !
To me, we need at least 22 nodes to chain of TIPS maintenance. At this exact moment I see only 5 active nodes to me. With this quantity of nodes the chain can be hacked easily with new forks. Because this the BlockChain of BTC is very trustable, isn't possible to control more than 50% of BTC nodes (is necessary enormous computation work), if someone keep the this control, is possible to join new chains (new hacked forks) on the real chain. Unfortunately after CRYPSY bankrupt, resposible for maintenance of important nodes of TIPS, we now have very little nodes... we need more nodes to combat 51% crypto attack.

Hello ppl

I am feeling  FedoraCoin suffering attack to force new forks (maybe attack to control 51% of nodes) and we are losing coins, so more some attacks and the coin will lose the value because the investors want trust chains... and FedoraCoin will turn into a shit coin. I sugest more nodes to preserve the chain.

and again Orphans and again we lost money !!!!!!!
and still from devs 0 info, no communications !!!
I saw in 2 and half years many bad people here in crypto but I have to say that this is one of the worst kind of people !!!

how come tips value so high atm?

TIPS pool on www.mining-dutch.nl is rolling blocks again,
We do not guarantee any fork issues that might occur. so mine at your own risk!!

So far so good.