Why is the chain broken? My wallet is not syncing and CANN is down for maintenance on Bittrex. Upgrade happening? Fork?
Where is your wallet getting stuck? I cannot get past block 1061756 when trying a full chain sync, checking the debug.log the next block has not been sent to my node at all. Last block in debug.log Block 1061756 000000008b4910ff2c3dc86de55e6a5b2892b3f3621ff6e61dfb109b3db130d5 Next block shown on https://chainz.cryptoid.info/cann/ not seen Block 1061757 00000000738d25e43fbc8c2eb99662bcd7d6e24f3bb06263242494be9ea9ef51 |
|
|
|
If anyone is interested in the benefits of segwit you can read the following article that covers the many pluses. It is no small thing to do but it is achievable and will add value to ArtByte. segwit benefitsAdding segwit would require a soft fork if done the same way as Bitcoin did with BIP148, it can be enabled when mining support for it reach a certain threshold. You can read more about it at the link below. UASF |
|
|
|
|
Are the golden days of crypto gone asked in 2014 when they had not even started! Actually the content seemed to be have the golden days of mining gone and if by golden days mean mining in your bedroom and making a profit then I'd say so for the most part.
Are there still amateur miners out there making a profit or is it all farms and ASICS?
As for crypto itself it has yet to really reach out into people's homes, but barriers to adoption are coming down and new innovative alts are coming out all the time. I'd say we still have the real golden days of crypto to come and not just participating in coin generation.
|
|
|
|
I've had a number of people approach me about their coins getting attacked by having the blockchain replaced with a longer chain, the longer chain released by the attacker is without certain transactions. The coin may be attacked but the target is normally an exchange, coins are sent to the exchange, sold for Bitcoin and then withdrawn, at that points the longer chain is released, the coins disappear from the exchange and the attacker gets their coins back. Small coins with low hash power are easy targets for attackers. This has caused a few coin pairs to be frozen and people to be in a panic. PoW coins are the typical target for this type of attack, PoS coins are harder to target due to PoS block generation but not impossible if PoS generation is still very low. There have been many proposals for solutions to protect coins from a blockchain replacement attacks but for small coins the one solution that works and is available now is to use live checkpointing. Checkpoints are defined in Bitcoin source code by defining a block hash and height, clients will only connect to a chain that has the corresponding blocks, it is to make sure that clients connect to the correct main chain. Altcoins inherit this checkpoint system. Realtime checkpointing was devised by SunnyKing developer of PeerCoin to protect the chain before PoS was sufficient. It protects the history of the chain by use of a node that will broadcast checkpoints at a certain height set in the conf file. If your coin is being attacked, your coin pair is locked on the exchange and you face potential delisting you may want to consider implementing realtime checkpointing. For reference there is a commit for checkpointing below (Deepcoin linked below was commissioned and not a project that I ran personally), instructions on how to use it is in the checkpointsync.cpp file. If you decide to use this system add a Peercoin copyright notice on the About dialog and COPYING file. https://github.com/Deepcoinbiz/Deepcoin/commit/43413fac89da1db064668e7e4dd5bd6c6036dfb4 |
|
|
|
|
It sounds like Bancor is going to be in competition with the Waves Platform. You can create your own tokens on each network and they can be exchanged within the system. Why use Bancor and not Waves?
|
|
|
|
|
Josh seems to be AFK, if anyone needs help with their coin give me a shout. I'm currently working on a hard fork one of his coins and getting it back up and running with DNS seeders so new clients automatically connect, pnSeeds as fall back, generating new CAlert keys to message the network, checkpointing keys for the ACP (Advanced Checkpointing) that was built in to the coin used but never used and setting up the ACP node.
|
|
|
|
|
Apologies if this has been asked before but can someone please clarify one point for me, is the currency for exchange always Ethereum?
In examples Ethereum is used and it is said that this will be deployed on the Ethereum network. If it is just Ethereum to start with will it expand to other networks later?
|
|
|
|
|
DNS seeders are back up and running so new clients will connect automatically.
|
|
|
|
|
What reference implementations of Bitcoin are most suitable for backing a front end service on to with a high user load?
Something that can be put onto our own AWS or Google Cloud hardware and support being scaled up to support high demand. The front end site will allow people to have their own wallet to pay others for work or product discounts or receive funds for those same things.
One options seems to be Bitcore which has come along way since I last used it. It is Node.JS which can be put on AWS Elastic Beanstalk and it uses MongoDB which can also be scaled on AWS. Are there others and please let me know if I'm wrong about Bitcore before I get too entrenched.
|
|
|
|
Ah well, we'll see if anything comes of it. The dev isn't paid to support users so I don't expect any technical response. That's one of the shortcomings here.
On another note, I guess the "rich list" is defunct and non-operational. My wallet made it's way into the top 100 ages ago and doesn't appear on the list. If this "rich list" is truly not working, then reference to it should be removed from the first post. As it is misleading.
 The DNS seeders, which are used by the client when it starts to look up other nodes on the network, were set to support the new test clients. They were set to no longer maintain a list of current clients which could have caused your connectivity problems. The seeders have now been set to fully support current clients again. Please let me know if your problem is resolved. |
|
|
|
|
I am in the process of adding SX to Deepcoin and have what I believe is now complete code. Tomorrow testing will commence on this new feature. The neat thing about this is that it can work on top of the existing network without the need for a hard fork.
Hopefully the next news you hear from me will be very positive.
|
|
|
|
Yes , Peter is lead dev of Bollywoodcoin now and in the future, using X11 this is not a feathercoin clone.
Alright, could you get him to verify this? Hi all, this is Peter Bushnell the Lead Developer of Feathercoin. I can confirm that I am the developer for this project, it is forked directly from Litecoin and uses X11+ for PoW hashing and DGW v3 for retargetting. We are calling it X11+ as I have corrected the error put into the first blended hash solution coin and copied into all the others. There are two functions for getting hashes in the code, one for PoW and the other for transaction hashing. The first blended hash solution overrode both of these so transactions are hashed in X11 which creates compatibility issues with third party systems like the Insight-API which the Insight explorer backs. Some history, Shahid first contacted me on BitcoinTalk but would not give me details of the project until he met me face to face. He travelled down from Scotland to see me which is no short trek to the South East of England. I am a bit of a cynic in crypto but Shahid has solid plans and wants to create a paid video service for Bollywood films. Bollywoodcoin would be the coin to be used and would be used to fund the project though at that point in time none of the finer details were clear. That is a few months ago now and the project is finally coming together at a rapid speed. Right now I am in the process of setting up the infrastructure for Bollywoodcoin by creating a web wallet, DNS seeder and explorer. I expect to be the developer of this coin for the foreseeable future. Hope this helps  |
|
|
|
|
I'm Peter Bushnell the Feathercoin Lead Dev and was commissioned to create Deepcoin in the first place and am here to support ongoing development. The plan is to implement stealth addresses into Deepcoin, these plans were delayed due to personal problems on my end for which I apologise.
It is sad to see the delistings as we move on to new features but I do not believe that this is the end, further technical development will return confidence to this coin and will hopefully have a positive effect on the market.
I am discussing future development plans now with DeepcoinBiz and will update you on progress.
|
|
|
|
♪ღ♪*•.¸¸¸.•*¨¨*•.¸¸¸.•*•♪ღ♪¸.•*¨¨*•.¸¸¸.•*•♪ღ♪•* ♪░ღ░♪░ ░H░A░P░P░Y░ ░F░O░R░K░ ░D░A░Y░ ░♪░ღ░♪ *•♪ღ♪*•.¸¸¸.•*¨¨*•.¸¸¸.•*•♪¸.•*¨¨*•.¸¸¸.•*•♪ღ♪•« Feathercoin is now on NeoScrypt, 64 blocks so far. All went as well as expected. If you have not updated then please do so now. If you are having trouble mining you could try one of the following pools below that is now on the new algorithm. Nut² Pools run by an IT Professional and long time Feathercoin community member Nut² PoolsCoinotron, well known. Has been the pool for many for years. Coinotron |
|
|
|
|
Scrypt mining will still work until we hit block 432,000, you can upgrade now and carry on as normal.
|
|
|
|
|
If money leaves crypto it will be a good thing. I see that there are three people in crypto, the enthusiasts, the idealists and those who want money. It is the later that has dominated for too long and some will go to any length to make a buck. We are working in open source software with absolutely none of the open source ethos. Anyone should be able to pick up the code and work on it as that is how you contribute to open source and others should welcome that. Instead each coin that comes to life generally seems to be out to destroy all others. This is simply greed, the same greed I saw with Bitcoiners when I first joined crypto, they said that there should only be one coin, Bitcoin. That is only an argument if you are looking at crypto from a market perspective, the more coins the thinner the market, the thing is that this is open source software and Bitcoin has to maintain a certain status quo. It is the alts that can break out and try new things that others including Bitcoin can incorporate. Alts have the same attitude of kill other coins to make their worth more. This kind of attitude is corrosive to crypto and will put people off when they only see hostility and abuse. Perhaps if Bitcoin goes back to being worth cents we can focus on features and functionality again.
|
|
|
|
Feathercoin 0.8.7.0 releasedThe NeoScrypt UpdateIt has been a long time in the works but we have finally got NeoScrypt and a GPU miner so we can now release the Feathercoin 0.8.7.0 client with NeoScrypt set to replace Scrypt on block 432,000, this should happen on the 26th October 2014. There is a Twitter countdown to the hard fork available here. NeoScrypt uses stronger components than the Scrypt we are familiar with. A key element of Scrypt is Salsa which adds memory complexity, the problem is that the version of Salsa in Scrypt is weak and has been broken by differential analysis which is why we see cheap and powerful ASICs. NeoScrypt uses a blend of Salsa and its successor Chacha set to a higher level of strength. In theory these two should not be broken for at least a decade, this gives better protection than simply adding hashing functions. However the goal is not simply to avoid ASICs forever as this may not be possible though ideally we want to stay in reach of as many people as possible without the need for expensive mining equipment. As the majority of people buying Scrypt ASICs are not doing so to mine Feathercoin and the fact that some very large ASIC suppliers will be releasing products soon it seems sensible to move algorithm now before we face the challenges that hit many SHA-256 alts when the SHA-256 ASICs hit. We are moving to a new tier of hashing where Feathercoin can be the leading coin. Please be aware that after the update your Scrypt mining setup will no longer work. You will need to use the new GPU miner that we have been developing for several months now. Not only do miners need to upgrade their software but pools do as well. Feathercoin DownloadsWindowsMacLinuxMiner DownloadsCPU Miner 2.4GPU Miner 3.7.7bNeoScrypt CPU miner (source)NeoScrypt GPU miner (source)Pool modulesNOMP MultiHashing PRStratum Algo ModuleStratum Mining RepoResourcesNeoScrypt, a Strong Memory Intensive Key Derivation Function (white paper)NeoScrypt - the latest proof of work algorithm (press release)NeoScrypt (source)
|
|
|
|
|
Good news everyone, we are now on version 0.8.6.3. This is not a major release and if you already have a working client installed you can skip this one, however if you are a new user or are unable to connect then this new release is for you.
What we have done is created a DNS seeder for the CannabisCoin network. When the client first connects to the network it asks the seeder for a list of other clients to connect to. Without a DNS seeder you will have problems connecting which is why there was addnode information shared on the first post in this thread, those addnode entries were a way of manually specifying other clients to connect to. We can now do away with addnode information as clients will now automatically connect to the network.
On top of this a small list of pnSeeds have also been defined in the client source code, these are simply other clients to connect to if the DNS seeder is down, it is like defining addnode information in the source code. This update is the first in many to help develop the CannabisCoin client and network.
Small point to note, the dark interface wallet has been retired. Alternative or improved interfaces will no doubt be returned to in the future.
In case you missed it I recently joined the CannabisCoin development team, I am the lead developer from Feathercoin where I still spend a lot of my time.
Keep watching for more updates soon.
|
|
|
|
|
Show Posts
