Looks like Cryptorush has pulled Funk for now (not that I'd really use them right now unless you like to gamble big time) Yesterday in IRC they were saying they were going to halt any coin that this attack can be used agaisnt until they are patched, as they don't want to enable anybody doing it to dump their coins.
I'm surprised that the news of the exploit just now taking off, BitcoinEXpress has been posting about it for over a month and even telling what needs to be done to fix it, and apparently has enough hash power that he can exploit it, and has a timewarp chain in progress on Aurora coin that is catching up. (he's agreed to back it off if they patch it like he's been trying to get them to do all this time)
For low hash rate coins, it sounds like he can warp them in just a few hours, and seems several other people are now exploiting that on those coins, thus all the halting of trading of those coins and them all scrambling to patch them.
I'll email rush and find out more. Pretty shit of rush (what do you expect), as I have several million in there. All the more reason to vote on comkort https://comkort.com/vote/#FUNK and mintpal https://www.mintpal.com/voting. The exploit has been out there for a while, it just wasn't obvious how feasible it was (I still don't think it's obvious). But it is an exploit and needs to be fixed. The sooner, the better I reckon. I'll try and get to it asap, but I want to include other stuff with the client update as well. EDIT: btw. Come hang out with the rest of the band on IRC. There's a few regulars there: https://webchat.freenode.net/?channels=cypherfunks |
|
|
|
|
I made some profits from altcoin trading recently, and it's all going to FUNK. Put in paid votes at mintpal & comkort. The rest of it, nicely covers seednode hosting for the next 2 months at least.
Band high five!
|
|
|
|
We may need to be looking at this problem, coins with KGW are being attacked!... Regarding Auroracoin TW exploit (Fix included) https://bitcointalk.org/index.php?topic=552895.0"The exploit BCX has found in KGW implememtation is real and, I believe, he is most likely attacking with the exploit just now..." Pandacoin was hit with an attempted attack last night.. Yes, it definitely affects all kgw currencies. Yep. Actually, the timing for this is good. A fix the KGW needs to be done BEFORE the android wallet is deployed. And Rush is doing maintenance on FUNK. Before we hit other exchanges, I think the timing is good to put a fix in for this. Other stuff I want to implement. And want your thoughts: 1) Add in the notification/alert system [#1 priority. This is so we can more easily inform users to switch when it is needed] 2) Raise the fees. The fees were never meant to be 0.001 [same as Litecoin]. It's supposed to be higher, closer to the soft dust limit [same as Dogecoin's fees]. Like what happened with doge, if FUNK becomes popular, a spam attack can happen on the network if we don't raise the fees. If you want to help! https://github.com/The-Cypherfunks/The-CypherfunksAnything else? I'm still adverse to changing the hashing algorithm. And I've explained why several times. It comes down to: asic-resistance will always be an uphill battle. Doing mobile development, I'm especially concerned how the hashing verification affects SPV syncing. SPV is supposed to be quick, not the days of syncing a full chain. I have no idea how X11 for example performs for SPV verification. You are doing a lot of expensive verification hashing. Scrypt-N with expensive external memory requirements sounds like a deathknell for mobile SPV wallets. Scrypt is already slower than SHA256 [substantially]. The other factor is simply: development time. Currently I'm spending most of my time doing development on Cypherfunks. Porting native hashing code over to android is just something I don't have time for. There is scrypt native code already. So that solves that. Also! Dig comkort. Thanks for voting Jommy! I will vote there as well, as well as on mintpal. Let's get the ball rolling, the beats dropping and rhythm flowing.  EDIT: Just to clarify. I'm going to study the TW exploit fully to see if it's needed. It is definitely an exploit, but if its attack vector is too large (like a 51% attack), then we'll reconsider. |
|
|
|
|
Just an update on the Android wallet.
Been busy putting up a proper DNS seed node so that the Android wallet can discover a lot more peers, instead of hardcoding it [which isn't future proof]. But DNS changes to nameserver take ages to propagate!
|
|
|
|
I still have a month or two before I want to be passing out Cypherfunks flyers at festivals!!
Mobile website and a QR-code on the flyer. Yeah, a simple one-pager will suffice. Great idea of including a QR code. |
|
|
|
I was sure I already posted here, but whatever A band of friends ( Gevelot) I recently introduced to Bitcoin talked to me about this project last night and it sounded interesting, different at least. I'll keep an eye on this. Good luck P.S. As you can see in my signature I'm trying to help them with first sales. A system like this would work greatly with your currency aswell. Think about it. Hey yeah! When I saw them on r/bitcoin, I pinged them. Donated some BTC too, and glad they added some tunes. Regarding sales. I created http://min.io. If resources come in [possibly creating an incubator for some companies with friends], we are repurposing Min.io to support loads of alt-currencies, the first being FUNK. btw, I see we've been steadily getting votes on mintpal! Cheers! https://www.mintpal.com/voting |
|
|
|
|
This is odd. Seems to be related to the 2^n transactions in blocks. Seems possible there's some flaw somewhere?
|
|
|
|
|
Bounty for the reddit tipbot has been paid. Thanks n00bnoxious!
|
|
|
|
Seems like it. Think it's mostly for-profit miners that left due to Rush not allowing LTC to get out. We need to get onto a new exchange.
I've been watching the whole Cryptorush circus for the last 48 hours including the whole IRC drama live. While there is a chance the new owner may turn it around, I'd not put anything into it until they are stable, unless you really like playing the odds. This affected a whole bunch of coins too. There was even a chance of Moolah.Io taking them over at one point but things just got shady and the offer was pulled and much drama resulted. The new owner kicked into action a bit ago, got the site itself stable but they are still running negative wallets on the major coins so be careful. Is there any statistics on the tipbot usage? Great work getting that up and running. If the bounty has been paid the main page needs to be updated that this is completed and paid, and credit given. It looks like the music side is doing pretty good. Lots of good stuff there. I'll pay out the bounty today! |
|
|
|
I almost forgot. There's a new exchange being created in the US by the dev of P$, AMK, and GOD. He and some other people are putting it together because they are sick of all the bullshit exchanges out there. I can't remember what it will be called, but I'll look it up. I can ask them when they get it up. Also, Atomic Trade seems to be another possibility, as they are quite reputable, albeit smaller.
Oh yeah. Bryce? I'll ping him. Also, I'll take a look at Atomic Trade as well [and contact them]. |
|
|
|
there is official price - Each 0.00010000 BTC received will count for 1 vote but maybe dev shous talk to owners and they agree to support FUNK for free or less cost? That's straight up bribery. Don't these people realize all the laws they are breaking? Just like the P&D guys. It will be interesting to see what happens to these people as regulators start taking action. The US FBI is seriously investigating the P&D guys. Imagine if you owned a company and you bribed your way on to your country's stock exchange. The same laws apply, it's just a matter of enforcement. Then again, this is the wild west and I suppose we can't really play by rules if no one else is. Hey Jeremy! Yes, that's a BTC address. And to clarify. You can vote by clicking or paying to get votes. They are just transparent about it: http://mintpal.com/voting. btw. I've started telling musicians the following: "The Cypherfunks is a world-wide band anyone can join and make music that is crowdfunded through a cryptocurrency, like Bitcoin." Or you can change the last part and say: "that is crowdfunded through a new type of digital currency." |
|
|
|
Only 5 MH/s network total? Is that right?
Seems like it. Think it's mostly for-profit miners that left due to Rush not allowing LTC to get out. We need to get onto a new exchange. There's some stuff in the pipeline I'm hoping to get off the ground soon (2 options regarding incubators) where we can get more support to fund this project. Tomorrow, I'll get back to the Android wallet. I'm just behind on my actual stuff due to the time spent on Cypherfunks.  |
|
|
|
|
So. An update on the Android wallet. Finally figure out what the bug was [it's not]. SPV nodes don't directly connect to other nodes, so they can do "getaddr". It requires either hardcoded nodes, or a dynamic DNS seed [which is what BTC has].
Do "host seed.bitcoin.sipa.be" and you'll see.
We don't have one. I'll try and get one online. If anyone still wants to donate to the hosting of seed & dns nodes, please do: 1Aowi9E4P4TpivyVWVRKxsQXcfP4FCmzKC.
But I'm behind on other stuff I need to do, due to working on the Android wallet. Will try and get it done asap.
|
|
|
|
I see you guys userfriendly, [If you don't add rpcallowip to localhost (if you are a solo miner), then it is HIGHLY recommended you change user and password, otherwise someone can connect to your node if the port is open for inbound connections.]
I'm currently completely out of sync. addnode=54.84.124.41
addnode=54.194.208.24
addnode=86.74.194.42
addnode=93.196.187.69
addnode=178.223.132.81
addnode=173.216.29.12
addnode=75.181.156.208 You don't mention any network port, there is only rpcport=23666. Here: https://github.com/The-Cypherfunks/The-Cypherfunks/I found: Ports: Main 33666. TestNet: 34666. I'm trying with and without this port ( 33666 ), anyway every host decline my connection. Could somebody share with me current valid nodes, peers.dat: $ ./Cypherfunkd getpeerinfo with valid ports ?? Hi! For addnodes, you don't need ports. Network ports are baked in. Old node IP sometimes still remain in the peer information in case it comes online somewhere in the future (so it seems like nothing is connecting). Here's a getpeerinfo dump from the seenode. [ { "addr" : "193.37.138.34:34599", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338865, "bytessent" : 97373, "bytesrecv" : 474274, "blocksrequested" : 15, "conntime" : 1396198326, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "198.23.178.33:33666", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 486189, "bytesrecv" : 141367, "blocksrequested" : 0, "conntime" : 1396198334, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "162.243.83.13:48332", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 429189, "bytesrecv" : 118613, "blocksrequested" : 0, "conntime" : 1396198347, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "188.226.187.110:58439", "services" : "00000003", "lastsend" : 1396338800, "lastrecv" : 1396338861, "bytessent" : 224337, "bytesrecv" : 160000, "blocksrequested" : 0, "conntime" : 1396198377, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "149.210.168.71:38189", "services" : "00000003", "lastsend" : 1396338962, "lastrecv" : 1396338861, "bytessent" : 876335, "bytesrecv" : 241914, "blocksrequested" : 2, "conntime" : 1396198419, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "188.40.98.213:33666", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 474081, "bytesrecv" : 410840, "blocksrequested" : 0, "conntime" : 1396198419, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "91.189.87.130:35303", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 866920, "bytesrecv" : 358634, "blocksrequested" : 1, "conntime" : 1396198442, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "76.97.138.180:51142", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 401291, "bytesrecv" : 287010, "blocksrequested" : 2, "conntime" : 1396198452, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26698, "banscore" : 0 }, { "addr" : "94.23.196.92:33666", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 663259, "bytesrecv" : 193949, "blocksrequested" : 1, "conntime" : 1396198502, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 26699, "banscore" : 0 }, { "addr" : "95.154.250.60:57674", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 692080, "bytesrecv" : 164065, "blocksrequested" : 1, "conntime" : 1396199040, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 26706, "banscore" : 0 }, { "addr" : "176.31.160.199:54910", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 576132, "bytesrecv" : 132707, "blocksrequested" : 1, "conntime" : 1396229002, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27016, "banscore" : 0 }, { "addr" : "67.231.54.2:55299", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 323754, "bytesrecv" : 288106, "blocksrequested" : 7, "conntime" : 1396233848, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27049, "banscore" : 0 }, { "addr" : "96.46.206.30:55645", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338862, "bytessent" : 379997, "bytesrecv" : 268046, "blocksrequested" : 0, "conntime" : 1396237351, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27067, "banscore" : 0 }, { "addr" : "185.36.72.65:41163", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 514572, "bytesrecv" : 153884, "blocksrequested" : 0, "conntime" : 1396242246, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27092, "banscore" : 0 }, { "addr" : "37.187.138.76:48059", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 202701, "bytesrecv" : 306194, "blocksrequested" : 0, "conntime" : 1396242399, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27092, "banscore" : 0 }, { "addr" : "54.194.208.24:53282", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 353886, "bytesrecv" : 67298, "blocksrequested" : 0, "conntime" : 1396277075, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27315, "banscore" : 0, "syncnode" : true }, { "addr" : "24.160.58.186:65452", "services" : "00000003", "lastsend" : 1396338965, "lastrecv" : 1396338861, "bytessent" : 98345, "bytesrecv" : 89312, "blocksrequested" : 3, "conntime" : 1396310612, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27582, "banscore" : 0 }, { "addr" : "176.196.176.201:33666", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 25331, "bytesrecv" : 25182, "blocksrequested" : 0, "conntime" : 1396335818, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 27753, "banscore" : 0 }, { "addr" : "81.101.133.53:52599", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 22970, "bytesrecv" : 8729, "blocksrequested" : 0, "conntime" : 1396336268, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27757, "banscore" : 0 }, { "addr" : "116.1.85.19:34024", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338334, "bytessent" : 17434, "bytesrecv" : 2326, "blocksrequested" : 24, "conntime" : 1396337213, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27753, "banscore" : 0 }, { "addr" : "93.81.39.79:40130", "services" : "00000003", "lastsend" : 1396338497, "lastrecv" : 1396338497, "bytessent" : 21703, "bytesrecv" : 352, "blocksrequested" : 0, "conntime" : 1396338483, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 0, "banscore" : 0 }, { "addr" : "86.144.48.108:33666", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338861, "bytessent" : 2074, "bytesrecv" : 8328, "blocksrequested" : 0, "conntime" : 1396338622, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : false, "startingheight" : 27780, "banscore" : 0 }, { "addr" : "116.1.85.19:34998", "services" : "00000003", "lastsend" : 1396338861, "lastrecv" : 1396338841, "bytessent" : 7284, "bytesrecv" : 172, "blocksrequested" : 0, "conntime" : 1396338840, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27781, "banscore" : 0 }, { "addr" : "196.210.98.226:62923", "services" : "00000003", "lastsend" : 1396338962, "lastrecv" : 1396338961, "bytessent" : 7223, "bytesrecv" : 1120, "blocksrequested" : 0, "conntime" : 1396338960, "version" : 70002, "subver" : "/Satoshi:1.0.0/", "inbound" : true, "startingheight" : 27782, "banscore" : 0 } ] Let me know if there is still something wrong. |
|
|
|
Update on the Android wallet. Trying to figure out a bug where the coins won't send immediately (when you close the app and re-open it sends the transactions). Coming soon, guys. Coming soon. |
|
|
|
|
Show Posts
