|
nice to see a good project like this. It will be very helpful for those who don't have enough time to spend confront of the computer and everything comes in a single platform. But how it's gonna intimate the user? via mail or sms?
|
|
|
|
Make sure that you download the client from the official website. artbyte.meThis may well be a false positive, we've seen these before. I will install one of the AV solutions that take offence and see what triggers them and what we need to do, we may need to submit a report to the AV company to get whitelisted. |
|
|
|
|
I do not understand the logic in a coin swap, there will be people left on the old chain and the new chain will be exploited at some point, spoofed NTP servers or something like that, are we going to coin swap every time?
If anyone ends up stuck on the old chain with redundant coins give me a shout.
|
|
|
|
|
So if it keeps the same chain but follows different rules it is a hard fork.
Why call all the coins to an exchange to handle it if it is the same blockchain?
|
|
|
|
It is not even could be considered as "free coins", the price of bitcoin is going to be split between bitcoin cash and the regular bitcoin, so you are actually not getting anything, just having your bitcoin being splitted into two different cryptocurrencies
Not really, BCC is going to be an alt with its own BCC/BTC pair on exchanges, it is not going to have the adoption, support or price of the official Bitcoin. |
|
|
|
|
Is the new coin that is being swapped for the current Dyn going to start from the genesis block again?
|
|
|
|
|
I am in the process of upgrading a couple of coins from 0.8 to 0.14 with CSV, Segwit and all other bells and whistles. These coins need to gain interest and support on the back of this work if it is to be a success. If no one notices and the coins do not gain use then there is little point in undertaking the work. I've been looking around for someone who does marketing for crypto and can assist with this. If anyone knows of someone or a team that is decent then please respond or send a PM.
|
|
|
|
|
I've been trying to get the attention of people on the official thread with no joy. Cannabiscoin Linux clients had an issue which caused them to get stuck, if you run a Cann server on Linux please pull the latest commits and recompile to get the chain syncing again, if you know how to contact someone running a Cann service please let them know.
The market is falling as people have probably noticed the Linux wallets stuck but it's totally unnecessary.
Quick summary of the problem, Windows was not following the checkpoint sync and ended up on a different longer chain, Linux disagreed and stayed on the checkpointed shorter chain. The new commit relaxes the checkpoint sync to allow Linux clients to fully synchronise. The network is still ticking and functional and has been this entire time but Linux has been left out of the party. Once updated they will resume functionality.
|
|
|
|
|
If anyone knows how to contact a service running Cann please contact them and let them know that they can pull the changes on Linux and compile it will start working again. The markets are freaking out, good time to buy!
|
|
|
|
|
It seems that checkpointing was not adhered to on Windows clients and when a longer chain came along they connected to it leaving Linux on the shorter fork. Windows clients show the same checkpoint as Linux clients but just ignores it. The checkpointing feature in Cannabiscoin was inherited from the source coin and looks like it is going to need some testing to make sure it works effectively across platforms. A temporary relaxing of checkpointing will be applied to the source to allow Linux to follow the longest chain and a solution will be found that gets both Windows and Linux to behave in the same way.
If you run a Linux node please pull changes and recompile.
|
|
|
|
|
There's a disagreement on the network between Linux and Windows wallets, Windows is on the longer chain while Linux rejects it. This is halting Linux wallets at block 2,264,246. Updating Windows wallet now to compare and find out where this disagreement stems from and how to resolve it.
|
|
|
|
Due to the recent attacks on several altcoins checkpointing has been enabled on UFO. Small coins with low hash power have been the target and rather than be the victim we are putting security in place. The checkpointing will prevent the blockchain from being replaced by an attacker, it effectively protects the history of the chain from being changed to roll back transactions. Some of the recent attacks have been devastating to coins and their communities. We do not plan to be victim to these attacks.  |
|
|
|
|
Chinacoin, I heard that they are going to use it as a national currency somewhere, cannot remember where, needs further research.
|
|
|
|
|
No this is not the launch of an alt with Tor, that's been done, but the question is whether anyone knows what the first altcoin with integrated Tor connection?
I'm trying to find the commit history for Tor integration but can only find alts with code dumps as their first commit.
|
|
|
|
I made a DNS seeder for this coin. https://github.com/Bushstar/Unidentified-SeederSet it up on the following domain from net.cpp. static const char *strDNSSeed[][2] = {
{"ufocoinnode.com", "ufocoinnode.com"},
};The format should be DN, FQDN, so if you add a subdomain seed1 it would be. static const char *strDNSSeed[][2] = {
{"ufocoinnode.com", "seed1.ufocoinnode.com"},
};Compile and release new clients and then they will connect automatically without having to mess with addnode entries in conf file. |
|
|
|
|
Are there any Bitcoin based altcoins with integrated smart contracts usable through the client GUI that are open source?
|
|
|
|
Update..
Managed to connect wallets and it's working fine.
Now the issue is i configured Max_Money 10Million and nsubsidy 1billion it means 100 percent premined at first block and 1 transaction for coinbase maturity.
But everytime i enter setgenerate true -1 in client consol new block is mined with another 10Million coins and all coins are immature.
Any help, how to set max money supply and 100 percent premined in src code i have done as following.
I want to make 10million coin maximum, 100 percent premined and no more than 10million coins can generate.
Your help will be appriciated.
Thanks in advance.
You want to do the following in the GetBlockValue in main.cpp, this will generate 10 million a block until after 100 blocks making 1 billion total. int64 static GetBlockValue(int nHeight, int64 nFees)
{
int64 nSubsidy = 10000000 * COIN;
if (nHeight > 100)
nSubsidy = 0 * COIN;
return nSubsidy + nFees;
} For the UPNP issue try replacing the USE_UPNP line with this one, it is what gets rid of your error for me. DEFINES += USE_UPNP=$$USE_UPNP MINIUPNP_STATICLIB |
|
|
|
Feathercoin was heavily attacked years ago, they really wanted us dead. The only way we managed to survive was to implement realtime checkpointing. Normal checkpoints are coded into the source like in the Bitcoin source below. It is simply a block number and its corresponding hash, clients will only connect to a chain with those blocks. https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L148Realtime checkpointing is where checkpoints are broadcast at a certain depth, the depth we used was five, this prevented an attacker from replacing the chain any deeper than those five block, exchanges then use a confirmation depth of six and then the coin cannot be used in a transaction reversal attack by replacing the existing chain with a longer one. I have linked in the code for this below on Deepcoin, I link that coin as the commit is relatively neat and encapsulates everything required. https://github.com/Deepcoinbiz/Deepcoin/commit/43413fac89da1db064668e7e4dd5bd6c6036dfb4I hope this may be of some help. All someone needs to do is add checkpointing to the coin, compile binaries and set up a node to broadcast checkpoints. People get funny about having a node broadcast checkpoints but the only other options seems to be delisting, there are elements of centralisation from source code developers to DNS seeders, sometimes the trade off is worth it. |
|
|
|
Feathercoin was heavily attacked years ago, they really wanted us dead. The only way we managed to survive was to implement realtime checkpointing. Normal checkpoints are coded into the source like in the Bitcoin source below. It is simply a block number and its corresponding hash, clients will only connect to a chain with those blocks. https://github.com/bitcoin/bitcoin/blob/master/src/chainparams.cpp#L148Realtime checkpointing is where checkpoints are broadcast at a certain depth, the depth we used was five, this prevented an attacker from replacing the chain any deeper than those five block, exchanges then use a confirmation depth of six and then the coin cannot be used in a transaction reversal attack by replacing the existing chain with a longer one. I have linked in the code for this below on Deepcoin, I link that coin as the commit is relatively neat and encapsulates everything required. https://github.com/Deepcoinbiz/Deepcoin/commit/43413fac89da1db064668e7e4dd5bd6c6036dfb4I hope this may be of some help. All someone needs to do is add checkpointing to the coin, compile binaries and set up a node to broadcast checkpoints. People get funny about having a node broadcast checkpoints but the only other options seems to be delisting, there are elements of centralisation from source code developers to DNS seeders, sometimes the trade off is worth it. @Bittrex: I've tried contacting you guys about these attacks but only get automatic responses from your email. I can offer to help coins that have been attacked at least use checkpointing, it will prevent chain replacement and in turn transaction reversal. |
|
|
|
|
Show Posts
