great  i have added the addnodes from Page 6 of this thread to the qt.conf in the Resources folder after right-clicking Show Package Contents. the Milo wallet is still showing no Active Connections to the network Any ideas what i should do? you need to add the nodes to a file called Milocoin.conf and put it in ~/Library/Application Support/Milocoin/ it's actually a minor pain in the arse to create such files in OSX. so here's one you can download, it has the two addnodes from the OP in it already https://drive.google.com/open?id=0B5j8d4FSc7drMUFNcm1ZbmhfVDgopen an explorer window, open the "Go" menu option , select "Go to Folder" enter "~/Library/Application Support/Milocoin/" that should take you to the default datadirectory, put the conf file in there. . I dont use default directories, so i'm not 100% certain that is the correct name, so IF "~/Library/Application Support/Milocoin" does not work, go to "~/Library/Application Support/" then browse to Milcoin folder. if you wanted to create the file yourself, (and assuming that ~/Library/Application Support/Milocoin exists as correct datadirectory) open a terminal window and enter touch ~/Library/Application Support/Milocoin/Milocoin.conf then browse there, open, enter addnodes |
|
|
|
i've never understood how to actually work out how long stakes will take .. but i've seen "time till stake" amounts being incorrect in many coins, one day i hope to actually appreciate the math involved i'm also waiting for the increasing weight to finally kick a PoS block .. the older your coins are, the more likely you are to stake .. but it certainly seems like the block time switchover really confused the difficulty adjustment and who knows how long it will take  -- amusingly enough, block 20000 was a PoS block and the difficulty was 78.1214 http://honey.thecryptochat.net/block/220b70009a3758dc126396d1bd8ea01d0960fdd734af860f72d9d492ecb5edc0now the difficulty is 1167.77608204 |
|
|
|
|
i dont think there's been a PoS block since "the issue"
|
|
|
|
Did you mean will give every our vote in c-cex exchange? Or that just example for us? Please correct me if I make mistake. Anyway for what that bitcoin address? the BTC address is for paid votes. it is a c-cex address. if you send it some BTC, it will go towards the voting process. |
|
|
|
87 Million Burned
Date: 3/8/2017 12:38
To: valtin VL3id6YsfM6AYVeRGBdF29fJPXAGxprfUu
Debit: -1.00 VC
Transaction fee: -87300642.63643251 VC
Net amount: -87300643.63643251 VC
Transaction ID: ea55efe32d053253128402e1874dc0c61adab33c89d8671f7d10ebda603db914
{ "hex": "010000000148c12e6a028a0b6927d238757a0caad57021675b98947e551f4b39493d0ccbc900000 0006c493046022100a0e7d1220305e7ad4edfd9cf93db1888a88f5a4edf47cfb148f78c522bdb53 c10221009bcc7d09421a8180dffe1ba49ebc64bb7085f38660f78b054f5efb74bfce87780121031 758a29c019d53ea96ef1a5244f965cca6df265403f2b84a7f2c4f346ba8a781ffffffff02017844 c2460800001976a91447e99ada6eb46968aefb6212b977ae3a7e63a7b588ac00e1f505000000001 976a91466fa3d3f723f9882170af7f3ccaca93a836f672b88ac00000000", "txid": " ea55efe32d053253128402e1874dc0c61adab33c89d8671f7d10ebda603db914", "version": 1, "locktime": 0, "vin": [ { "txid": "c9cb0c3d49394b1f557e94985b672170d5aa0c7a7538d227690b8a026a2ec148", "vout": 0, "scriptSig": { "asm": "3046022100a0e7d1220305e7ad4edfd9cf93db1888a88f5a4edf47cfb148f78c522bdb53c102210 09bcc7d09421a8180dffe1ba49ebc64bb7085f38660f78b054f5efb74bfce877801 031758a29c019d53ea96ef1a5244f965cca6df265403f2b84a7f2c4f346ba8a781", "hex": "493046022100a0e7d1220305e7ad4edfd9cf93db1888a88f5a4edf47cfb148f78c522bdb53c1022 1009bcc7d09421a8180dffe1ba49ebc64bb7085f38660f78b054f5efb74bfce87780121031758a2 9c019d53ea96ef1a5244f965cca6df265403f2b84a7f2c4f346ba8a781" }, "sequence": 4294967295 } ], "vout": [ { "value": 91000.00000001,
"n": 0, "scriptPubKey": { "asm": "OP_DUP OP_HASH160 47e99ada6eb46968aefb6212b977ae3a7e63a7b5 OP_EQUALVERIFY OP_CHECKSIG", "hex": "76a91447e99ada6eb46968aefb6212b977ae3a7e63a7b588ac", "reqSigs": 1, "type": "pubkeyhash", "addresses": [ "VHDTkNgNFi6LVpfbjasgSGiSpjEeKKR1qE"
] } }, { "value": 1, "n": 1, "scriptPubKey": { "asm": "OP_DUP OP_HASH160 66fa3d3f723f9882170af7f3ccaca93a836f672b OP_EQUALVERIFY OP_CHECKSIG", "hex": "76a91466fa3d3f723f9882170af7f3ccaca93a836f672b88ac", "reqSigs": 1, "type": "pubkeyhash", "addresses": [ "VL3id6YsfM6AYVeRGBdF29fJPXAGxprfUu" ] } } ], "blockhash": "00000000007d601dfd59ffd96a51f6e7f0e542bc9fb1a534106671ad063029a5", "confirmations": 1856, "time": 1489005531, "blocktime": 1489005531 } so only 91000 left out of the 387420489.00000000 premine, great work http://84.200.210.130:3001/richlist- i've always said there's nothing necessarily wrong with a pre-mine, only how it's dealt with. a 387million coin premine was a tad extreme when only about 50k has been distributed. having that amount of coins lurking in the dev fund was always going to raise issues. |
|
|
|
|
fees are burned,
so obviously setting the txfee as 100mill (or whatever) will destroy those coins ..
here is the premine transaction, prior to the "burning"
{
"hex": "01000000011dc41f0fb965a4374a8f3a1246bb503407af4d61f3bb6ecb1ef059ff776986e201000 0006b48304502210094c1995733024f2e42c5fb540caa11ab830616b4980407a051b163b313ed4b 1b02200666397b39089ac63a36aa4eec44482c1139d7c43650e7acb19b555f3e28bc83012103e48 9397c15aa4d72107a48097b5a2ff111bc139415bdfa2ae16ef2078f1b0752ffffffff020010a5d4 e80000001976a9140c25db4cc35cf971d22afe0e3f75df8ad5785f6288ac71fcaba410a18900197 6a914eecaed063f3baedfbc2ecda542afc95b7eb1ab6388ac00000000",
"txid": "e3b405db1391d9c5913ea71bde446d5841c9787c9b33869191914db79ccbcdb2",
"version": 1,
"locktime": 0,
"vin": [
{
"txid": "e2866977ff59f01ecb6ebbf3614daf073450bb46123a8f4a37a465b90f1fc41d",
"vout": 1,
"scriptSig": {
"asm": "304502210094c1995733024f2e42c5fb540caa11ab830616b4980407a051b163b313ed4b1b02200 666397b39089ac63a36aa4eec44482c1139d7c43650e7acb19b555f3e28bc8301 03e489397c15aa4d72107a48097b5a2ff111bc139415bdfa2ae16ef2078f1b0752",
"hex": "48304502210094c1995733024f2e42c5fb540caa11ab830616b4980407a051b163b313ed4b1b022 00666397b39089ac63a36aa4eec44482c1139d7c43650e7acb19b555f3e28bc83012103e489397c 15aa4d72107a48097b5a2ff111bc139415bdfa2ae16ef2078f1b0752"
},
"sequence": 4294967295
}
],
"vout": [
{
"value": 10000,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 0c25db4cc35cf971d22afe0e3f75df8ad5785f62 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9140c25db4cc35cf971d22afe0e3f75df8ad5785f6288ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"VBmTPEFqgbWcukqBa7P85z3M2ABcXsHX2x"
]
}
},
{
"value": 387391646.63643247,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 eecaed063f3baedfbc2ecda542afc95b7eb1ab63 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914eecaed063f3baedfbc2ecda542afc95b7eb1ab6388ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"VYRqqo3VmixWsZCAKrQkZjJ62gf6sYaanS"
]
}
}
],
"blockhash": "0000000002a5e758c5045debbdbf41531b9e0bc5e79e6df9903d7d93fdee0fdf",
"confirmations": 2161,
"time": 1488911208,
"blocktime": 1488911208
}
the output value of interest is
"value": 387391646.63643247,
then 1 coin is sent to VJ89GSirqkNVrRGJFzMyQ12iNmCBGoJPuU,
and the change is sent to VRYS6kBAXnsGi3pk3iVEBYRRvknbLSAPdm
the change is only
287391645.63643247
so 100million coins did disappear in the transaction.
{
"hex": "0100000001b2cdcb9cb74d91919186339b7c78c941586d44de1ba73e91c5d99113db05b4e301000 0006a47304402204f6c78ddee18711e6ce43413e313996a7da96f95899a6982b9e5e99582d583b4 022057a02b2bb754e6a3bc6df4405b90aa163cf22239f0f7d2c3c15dad784a1be39b012103304d1 5ad4f16a8445d0933bceaf4c08f30ec14a0c94d8fc2d632885d2c8ad2caffffffff02721bf52e1e 1a66001976a914a341235ae3da1c3447926656bf3fbc1cf52cb32a88ac00e1f505000000001976a 91451e039267f51ef38dd8c63af46ce23e7eb058a9888ac00000000",
"txid": "f251aa6066e5562373069c5971f942fc540b88e90cb84b1b9d3827059e4afb84",
"version": 1,
"locktime": 0,
"vin": [
{
"txid": "e3b405db1391d9c5913ea71bde446d5841c9787c9b33869191914db79ccbcdb2",
"vout": 1,
"scriptSig": {
"asm": "304402204f6c78ddee18711e6ce43413e313996a7da96f95899a6982b9e5e99582d583b4022057a 02b2bb754e6a3bc6df4405b90aa163cf22239f0f7d2c3c15dad784a1be39b01 03304d15ad4f16a8445d0933bceaf4c08f30ec14a0c94d8fc2d632885d2c8ad2ca",
"hex": "47304402204f6c78ddee18711e6ce43413e313996a7da96f95899a6982b9e5e99582d583b402205 7a02b2bb754e6a3bc6df4405b90aa163cf22239f0f7d2c3c15dad784a1be39b012103304d15ad4f 16a8445d0933bceaf4c08f30ec14a0c94d8fc2d632885d2c8ad2ca"
},
"sequence": 4294967295
}
],
"vout": [
{
"value": 287391645.63643247,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 a341235ae3da1c3447926656bf3fbc1cf52cb32a OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a914a341235ae3da1c3447926656bf3fbc1cf52cb32a88ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"VRYS6kBAXnsGi3pk3iVEBYRRvknbLSAPdm"
]
}
},
{
"value": 1,
"n": 1,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 51e039267f51ef38dd8c63af46ce23e7eb058a98 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a91451e039267f51ef38dd8c63af46ce23e7eb058a9888ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"VJ89GSirqkNVrRGJFzMyQ12iNmCBGoJPuU"
]
}
}
],
"blockhash": "0000000000b74179d2c144292daa2033bd22bb8a1b6d1956b718f16ab3a7d507",
"confirmations": 1879,
"time": 1488995319,
"blocktime": 1488995319
}
|
|
|
|
100 Million Burned
Date: 3/8/2017 12:35
To: gregofdoom VPpN8uAbY9XizSTLY7AWvA35A6AnFdRu8b
Debit: -1.00 VC
Transaction fee: -99999999.99999999 VC
Net amount: -100000000.99999999 VC
Transaction ID: c9cb0c3d49394b1f557e94985b672170d5aa0c7a7538d227690b8a026a2ec148
87 Million Burned
Date: 3/8/2017 12:38
To: valtin VL3id6YsfM6AYVeRGBdF29fJPXAGxprfUu
Debit: -1.00 VC
Transaction fee: -87300642.63643251 VC
Net amount: -87300643.63643251 VC
Transaction ID: ea55efe32d053253128402e1874dc0c61adab33c89d8671f7d10ebda603db914
100 million burned
Date: 3/8/2017 12:13
To: apple_talk VJ89GSirqkNVrRGJFzMyQ12iNmCBGoJPuU
Debit: -1.00 VC
Transaction fee: -99999999.99999999 VC
Net amount: -100000000.99999999 VC
Transaction ID: 0c5561f9202cbee5e4ee3bd6e9c1c3aa0f86e78648e3109f39ed141fa95bb3c3
Burning process started:
Date: 3/8/2017 09:42
To: apple_talk VJ89GSirqkNVrRGJFzMyQ12iNmCBGoJPuU
Debit: -1.00 VC
Transaction fee: -99999999.99999999 VC
Net amount: -100000000.99999999 VC
Transaction ID: f251aa6066e5562373069c5971f942fc540b88e90cb84b1b9d3827059e4afb84
|
|
|
|
I support the roll back. Arguments of blockchain immutability are irrelevant here as the attackers actions rendered the blockchain mutable
No , the attacker found an exploitable bug, and the blockchain is being rewound to undo it, but now we all can ask, 'what else would warrant rewind of blockchain', and this is the problem. invoking the slippery slope fallacy? the fear of centralised control vs hyperinflation via malicious exploit, hardly seems a reason to fear big brother fucking with our chain. |
|
|
|
closes in just under 3 days ... |
|
|
|
why sha256 huh?? provided for asic miner
Probs because everyone owns a sha-256 and scrypt ASIC even if they are ancient, shit everyone will own a X series ASIC soon  i dont know about everyone, but there is enough out there to keep mining going, then there's staking for everyone else .. |
|
|
|
Unfortunately during last 10 days we was really concerned about the future of the coin, the whole project was put in discussion by several problems:
first the difficulty that retargeted very slowly causing blocks of the network and transactions stuck on the blockchain. While working on this, we had a sever attack to the blockchain.
When finally both problems where solved, Cryptopia decided to close the market for more than 3 days, freezing funds of lots of users, locking deposit and withdraw without any further notice.
Thats caused a fall on interest of the coin, miners stopped or paused to mine the coin, volume crashed to zero...and everything happened just on the moment when the interest of coin started to rise up again with a price stable daily increase.
After that, was impossible for me and who is helping me on that project to also think what to implement new,what to develop first, which exchange contact to add us...then also plaina signature campaign for a coin completely freezed was not easy as the whole project was put in discussion.
Now we only hope that this project will not be called again to face some other problems.
my amended version ... When finally both problems where solved, yet another problem became obvious when exchange transactions were noticed to be changed and Cryptopia closed the market for more than 3 days, freezing funds of lots of users, locking deposit and withdraw without any further notice whilst they dealt with other important issues and also the effect of the fork on their books.The combined effects of these calamities caused a fall on interest of the coin, personally i have found Cryptopia to be trustworthy and responsible. i believe the fork came at a bad time for numerous reasons, one of which was that Cryptopia was in the middle of an important upgrade which could not be ignored. i have no idea if Cryptopia would have dealt with the issues more speedily at any other time, but the simple fact is that SFC forked and Cryptopia was effected. then they dealt with it. |
|
|
|
DavidSantamaria, i should've sent you a pm too, here's a mac wallet i built a few days back .. google do virus checks files before allowing download   . chain is still stuck on block 2714 |
|
|
|
DavidSantamaria, i should've sent you a pm too, here's a mac wallet i built a few days back .. |
|
|
|
**STATEMENT** From today, trading and market operations for $SFC on @Cryptopia_NZ are officially back to normal. Thanks for your patience
woot  |
|
|
|
|
the chain and coin are fine,
it is only cryptopia that are having problems.
it has nothing to do with the SFC team,
and is up to cryptopia to work out when and how they will deal with any issues.
SFC is by nature a de-centralised currency (although like many coins, attached to a development team),
but
by using Cryptopia (or other exchanges) you are operating within a centralised system,
by using Cryptopia you are subject to their conditions, and you do not have sole right to what you might consider as your property.
thems the breaks.
|
|
|
|
|
Show Posts
