LOL. It is not good to hijack coin from the developer.  Because coin without active developer is dead "a priori". Agree, not sure why folks are still pushing this hijack idea. |
|
|
|
I feel like the hijacked launch would be more fair than trying to restart things.
Letting it ride shows you weren't trying to tune in your setup or planning a major stash or anything shady.
What are your reasons at this point for wanting to start it over?
~richgene
A launch that is perceived to be fair is in the best interest of this coin. If some miners want to jump the line, well all I can say is that their coins aren't going to be valid if they tampered with the original source code. You are not in control and/or relevant for this coin anymore; we took over. Support this launch or start over with a new coin, it's your choice. You and eagle should first pause your mining operations, allow us to verify the binary and we can negotiate if the coins you have already mined are to be made official. |
|
|
|
|
ZTC - Demand is overflowing that folks are mining the coin even prior to official launch.
|
|
|
|
I feel like the hijacked launch would be more fair than trying to restart things.
Letting it ride shows you weren't trying to tune in your setup or planning a major stash or anything shady.
What are your reasons at this point for wanting to start it over?
~richgene
A launch that is perceived to be fair is in the best interest of this coin. If some miners want to jump the line, well all I can say is that their coins aren't going to be valid if they tampered with the original source code. |
|
|
|
In the footer of the Zenithcoin page, it says FrictionlessCoin.
Now that the community has taken ZenithCoin and run with it, why don't you just re-release it with your originally intended name or the name for whatever WordPress coin theme you used?
~richgene
The biq question here is whether this hijacked launch was a fair launch or not. This is a good pre-launch test in my opinion. You simply were not stay in launch ... {
"version" : 70200,
"protocolversion" : 60002,
"walletversion" : 60000,
"balance" : ".00000000",
"blocks" : 9321,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.01562500,
"testnet" : false,
"keypoololdest" : ,
"keypoolsize" : 101,
"paytxfee" : "0.00000000",
"errors" : ""
}
Well that's a nice collection of newly minted *test* ZTC. I suggest waiting for the official launch. |
|
|
|
Haha, community called a mutiny on the coin.
~richgene
I know everyone eagerly wants to see the coin launched, but skipping the line is frowned upon in many cultures. Anyway, test mine as much as you want. This coin however is extremely difficult to hi-jack without the developers support. |
|
|
|
In the footer of the Zenithcoin page, it says FrictionlessCoin.
Now that the community has taken ZenithCoin and run with it, why don't you just re-release it with your originally intended name or the name for whatever WordPress coin theme you used?
~richgene
The biq question here is whether this hijacked launch was a fair launch or not. This is a good pre-launch test in my opinion. |
|
|
|
ZenithCoin v1 is launched! The creator, solracx, wants to restart the coin while over 9000 blocks are mined. By generating the Genesis block and stating " Launch Date Jun 1, 2013" it's officially launched! current block : 9163
current difficulty : 0.01562500
block reward: 12
He'll haves to start over with a new name, ZenithCoin is taken over by the community! Port: 9737 (forward in your router) RPCPort: 8332 (point your miner at this port) Content of zenithcoin.conf below: rpcuser=username
rpcpassword=password
rpcallowip=192.168.*.*
rpcport=8332
daemon=1
server=1
gen==0
addnode=54.234.70.232
addnode=54.215.138.30
addnode=24.209.133.75:55352
addnode=88.8.135.205:61238
addnode=2.13.131.115:61938
addnode=54.215.137.78:59885
addnode=50.16.207.95:51039
addnode=113.162.188.201:57968
addnode=24.6.21.198:49291
addnode=124.183.82.151:57014
addnode=78.193.10.34:9737
addnode=142.59.183.52:49326
Original source location: https://github.com/zenithcoin/ZenithCoinSource master: download linkWindows client (9.3 MB) compiled by eagleEye: download linkHappy mining! Disclaimer: As much as I do appreciate the interest in this coin, this is not an official launch. Furthermore, I cannot validate the integrity of the binary distrubuted here. |
|
|
|
This has got to be a first! Alt-coin hijacked prior to official launch! |
|
|
|
Windows Qt client is on, and Coin is launched as long as it is been adopted by users. So this is the bitcoin realm.
You can test mine to your heart's content. Thank you for creating coins that we can test with. |
|
|
|
Yes, this will appeal to miners who understand the value proposition.
You don't need windows-qt to mine the coin.
Lack of a windows binary is a sure sign of developer incompetence. Lack of a windows binary only means that it is not is the list of high priorities. It's not a high priority to compile a client that 90% of this forum needs? What the fuck are your priorities then?  Ok. We will change our priorities here. I just realized that alot of mining is performed by gamers who have windows machines and apparently need a UI interface. Ok... 500 ZTC bounty for a compilation and binaries of the QT client. But, I will have to check in the code for the QT client first. The plan was to have a MultiBit client for Windows, MacOS X and Linux. But we can have a windows QT client in the interim prior to launch. |
|
|
|
|
Well that's a lot of blocks that you've mined. All I can say is "thanks for testing out the coin".
|
|
|
|
Particural terminology eh? solracs quote: but we'll recreate the genesis block on the official mining launch so you will will lose these test coins so you will will lose these test coins so you will will lose these test coins so you will will lose these test coinsI could be wrong though, english is not my native language  Coins are in blockchain ... Creators likes to play with miners, it is a known fact I know it is really exciting to get a jump on everyone, but as stated earlier, the coins that you mine now are not going to be valid when the coin is launched for mining. Also, users need to be very careful about binaries that do not come officially from the source. Thank you for your interest though. |
|
|
|
It seems at that point that all the block chain and miners are doing is helping users order transactions that it doesnt know much about.
In Bitcoin the miners are responsible for creating the block and therefore ensuring the transaction inputs and outputs all balance out and performing other validation checks prior to inclusion into a block. Are you saying that there are no validation checks for a transaction to be included in a block? I am saying it is possible to leave the validation to the transacting parties. The spender just reveals the input transactions to the recipient, the recipient checks the validation and that the transactions are on the block chain (in hashed form) accepts or not accordingly as usual. You shouldnt ideally be relying on a few powerful miners to do validation anyway if the miner is dishonest or more likely hacked you can accept fictitious bitcoins that weren't mined. SPV clients do rely on this because they dont have enough bandwidth. You can decommit the hashed coins to help SPV clients as then most transactions can be validate by the miners (all the old decommitted ones). The only coins that cannot be miner validated are the ones that have not yet been decommitted. (How many times user respend in committed form without decommitting is up to them, though such coins are a bit less SPV friendly.) Adam As I understand it, miners validate each other's work in the bitcoin network. So even if a powerful miner builds the block, other miners verify the block after creation. So in your scenario, how do the miners keep a check on each other? That is, if there is nothing to validate, what then do they check to see if nobody is attacking the network? |
|
|
|
I see 2 fatal flaws without even looking into it in more detail:
1. 50% of all coins go to the developers. For this alone I will never mine this coin. The concept isn't actually a bad one but instead of keeping 50%, maybe 0.5% would be "reasonable".
2. No Windows-qt. This gives everyone that is not using Windows a huge head start. Someone will make the Windows client but by then everyone else will have raped the coin.
So for me for the first reason alone, I will never support this coin. And that is saying something because I have almost every wallet in existence.
Yes, this will appeal to miners who understand the value proposition. You don't need windows-qt to mine the coin. True. In the same way that you CAN accept only Diner Club at your store, but 9/10 people will think you are out of your mind and walk away. Now after thinking about it, a Windows-QT may be necessary. I think there are a lot of casual miners out there that use their game boxes to mine. |
|
|
|
You need to install the gmp libraries.
sudo apt-get install libgmp3-dev
Hm..aint that for mp3? Edit: No its not This worked for me: sudo apt-get install libgmp-dev && sudo apt-get install libmpfr-dev Yes, that looks right. Just a disclaimer, you can test mine right now, but we'll recreate the genesis block on the official mining launch so you will will lose these test coins. Thanks for your interest. |
|
|
|
You gotta love the fuckups in the initial commit: [b]gensis[/b] block created #define COIN_DNS_SEED {"node.[b]zenitcoin[/b].com", "seed.zenithcoin.com"},Move along, nothing to see. Just another failed altcoin done by a toddler. Well thanks for the second catch. The DNS seed is not yet working. The default setting will first be IRC (like the original Bitcoin). (Reminder to self: set this up prior to mining launch) It indeed is interesting that the current Bitcoin defaults are not applicable for a newly created coin. |
|
|
|
I got the following error when trying to compile the daemon in Ubuntu 12.04: In file included from netbase.h:10:0,
from util.h:30,
from alert.h:13,
from alert.cpp:8:
serialize.h:281:19: fatal error: gmpxx.h: No such file or directory
You need to install the gmp libraries. sudo apt-get install libgmp3-dev |
|
|
|
I have finally started that "bitcoin with ONLY the merged mining parches applied" repo I have so often mentioned. https://github.com/knotwork/MergecoinThe purpose of this repo is to provide the common code that all merged mined coins based on bitcoin all have in common, that is, bitcoin plus being able to be a secondary coin in a merge. Most merged mined coins will be trivially easy to update to recent bitcoin code using this repo once the repo is ready and debugged. Namecoin and Devcoin, being more than trivially different from bitcoin, will take more work to update, as they have more things they need to change. But most will be able to update as fast and easy as the creation of pump and dump coins shows us almost anyone can easily do. Problem is, recent bitcoin is quite a bit different from the ancient version the merged-mining.patch was based on, so just getting the merged mining patches all applied is going to take some work... -MarkM- auxpow? cryptopp/sha.h? looking forward to the updates. |
|
|
|
I have finally started that "bitcoin with ONLY the merged mining parches applied" repo I have so often mentioned. https://github.com/knotwork/MergecoinThe purpose of this repo is to provide the common code that all merged mined coins based on bitcoin all have in common, that is, bitcoin plus being able to be a secondary coin in a merge. Most merged mined coins will be trivially easy to update to recent bitcoin code using this repo once the repo is ready and debugged. Namecoin and Devcoin, being more than trivially different from bitcoin, will take more work to update, as they have more things they need to change. But most will be able to update as fast and easy as the creation of pump and dump coins shows us almost anyone can easily do. Problem is, recent bitcoin is quite a bit different from the ancient version the merged-mining.patch was based on, so just getting the merged mining patches all applied is going to take some work... -MarkM- Seems to have failed compilation on MacOS X. |
|
|
|
|
Show Posts
