[TAKEOVER]

TAKEOVER

Shift is the first fork of ethereum and was the first to release a GUI wallet.

The original Shift developer has admitted to spending the entire premine, but did little to develop the currency itself. After disappearing for several weeks, the original developer reemerged after the second ethereum clone, expanse, exploded in price. He now asks for bounties in advance of any development.

The original developer's highly suspect actions suggest that he can not be trusted with further funds. This thread has been started to keep Shift alive and on a positive development trajectory.

The proposal is as follows:

1. Fork the Shift repositories in case the original developer takes the old ones down in spite (done).
2. Find a competent development team to adopt the project.
3. Fund this team using community donations to a block chain escrow account that is controlled by community consensus.
4. Lock the block chain by hard checkpoint onto the new development tree, preventing any malicious attempts by the former developer to undermine the currency with bad releases.
5. Attempt to get bittrex to convert to the new development tree. If they refuse, find other exchanges that will use it. This may result in a fork at some point, at which time the most active development tree will likely be adopted by all exchanges.

The new github repository is here: https://github.com/shift-takeover/

Please remember the new development tree has not been adopted yet by any exchange.

Currently, the only thing required of the community is to begin activity in this new thread.

 
 
SPECIFICATIONS
 
Mining Algorithm: ethash, Initially Proof-of-Work, later Proof-of-Stake or hybrid PoW-PoS
 
Target Block Time: 25 seconds




SHIFT NODE SOFTWARE v0.4.0
 
Download on GitHub

When downloading the binaries from GitHub make sure to left click and go all the way to the RAW button




SHIFT GUI WALLET v0.9.3
 
Download on GitHub
 
When downloading the binaries from GitHub make sure to left click and go all the way to the RAW button
 
 
 
 
MINING
 
Number of SHF mined at minimum: 2 000 000
 
Estimated number of blocks / day (including uncles): about 3456
 
Estimated SHF mined / day: 10368
 
Block reward: 3 SHF
 
 
 
 
POOLS
 

 
 
 
ECONOMY

Premine: 250 000  The premine has been spent.
 
Bounty funds: We will be establishing a block chain smart contract to handle community provided development funds. Spending will be approved by community consensus.



BLOCK EXPLORER

COMING
 

MISSION
 
SHIFT is based on Ethereum and represents its first fork. This enables smart contracts and a full turing-complete
contract programming language.
 
SHIFT will offer bounties for individuals that help the network grow by pushing decentralized applications onto the
SHIFT blockchain. Our aim and hope is to make SHIFT a competitively sized network in regards to number of nodes
and dapps.
 
Next to the internal developments we are looking to actively sponsor and incentivize a continuous and rapid evolution
of the platform via bounties and development funds, provided from the existing premine.
 
After a minimum of 2 Million SHF mined, holders will have the ability to vote on future means of
distribution, i.e. when and how a switch to a pure PoS or hybrid PoW-PoS system will take place.
 

 
 

EXCHANGES
 
 

       
 

 

INFORMATION
 
If you are running your Shift node on a server directly connected to internet, make sure not to enable RPC if you do not firewall that port.


 
 
https://github.com/shift-takeover/shift/wiki/Installation
https://github.com/shift-takeover/shift/wiki/CLI---Command-line-interface
https://github.com/shift-takeover/shift/wiki/Console-commands
https://github.com/shift-takeover/shift/wiki/Mining

 
 

Follow us on Twitter

We all know the ugly face of "censorship", where troll posts are deleted from a topic.

To battle "censorship" of this manner, please when you delete a troll post from your topic, post them here so that trolls don't feel like they are "censored".

Also, if you are a troll, please check the list of posts here to see if any are an exact copy of what you are going to post. Then, you may refer to it by number and save yourself from duplicating the work of your troll peers.

Also, this is a self-moderated topic. If you post something that looks trollish, I'm going to delete it. But the good news is that you can troll post just about anywhere, so no one is encroaching on your rights, or whatever.

[If you have a screenshot of the voting from before the incident, please provide it!!!]

The mintpal voting system has been hacked.

Several coins have mysteriously switched position over the last couple of hours, one losing 15 to 20 thousand votes.

This points to a serious security breech.

Mintpal has nothing to say on the topic.

If you have a screenshot of the voting from before the incident, please provide it!!!

[42 Has Fixed This Problem]

42 Has Fixed This Problem

Introduction

With a market capitalization ranking of 61[1], the coin "42"[2] is advertised as the "Highest Priced Crypto Coin Ever"[3]. This high price is attributed to the coin's rarity, which is advertised to be limited to 42 total coins. Unfortunately, it looks like 42 coin and descendents thereof (like 8 coin) do not cap the money supply at the advertised number of coin. In fact, unlike most cryptocoins, the money supply of 42 appears to be unlimited.

Money Generation

In bitcoin and most descendents the money supply is capped algorithmically in the function that calculates the mining subsidy. This function is called GetBlockValue() in the source file "main.cpp". In the bitcoin code base, the source for this function is:

Code:

int64_t GetBlockValue(int nHeight, int64_t nFees)
{
    int64_t nSubsidy = 50 * COIN;

    // Subsidy is cut in half every 210,000 blocks which will occur approximately every 4 years.
    nSubsidy >>= (nHeight / Params().SubsidyHalvingInterval());

    return nSubsidy + nFees;
}

Here, the subsidy is halved for each "halving interval", measured in blocks (although the calculation is obfuscated somewhat for the sake of computational efficiency). It can be proven[4] that if all halving intervals are the same length (210,000), then the maximum amount of bitcoin ever produced will be

    21,000,000 = 2 * 50 * 210,000

42 (and probably several descendants, such as 8) uses a GetBlockValue() function like the following, taken from the 42 code base:

Code:

int64 static GetBlockValue(int nHeight, int64 nFees)
{
    int64 nSubsidy = 0.000042 * COIN;
    if(nHeight < 419)
    {
       nSubsidy = 0.0000001 * COIN;
}
    if(nHeight == 1)
    {
       nSubsidy = 0.42 * COIN;
}
    if(nHeight == 420) // yay its 420 :) Time for a smoke
    {
       nSubsidy = 0.00042 * COIN;
}
    if(nHeight == 4242)
    {
       nSubsidy = 0.00042 * COIN;
}
    if(nHeight == 42424)
    {
       nSubsidy = 0.00042 * COIN;
}
    if(nHeight == 424242)
    {
       nSubsidy = 0.00042 * COIN;
}
    if(nHeight == 4242424)
    {
       nSubsidy = 0.00042 * COIN;
}
    return nSubsidy + nFees;
}

Except in a few cases (blocks 1-420, 4242, 42424, ...) all blocks will have the same reward of 0.000042 coin (ignoring fees). Notice that the 42 version of GetBlockValue() has no halving interval and makes no attempt to curtail coin generation at the advertised maximum of 42 coin. Without a geometrically decreasing reward value, the money supply will grow indefinitely.

For 42, the advertised coin maximum of 42 coin will be produced before block 1,000,000 (42 / 0.000042), or in about 1.33 years. But the existing 42 code makes no provision to stop coin production at that time.

MAX_MONEY

One part of the code for most cryptocoins that may be confusing to developers is the MAX_MONEY constant in the source file called "main.h". MAX_MONEY has two uses in the 42 code: (1) as a sentinel return value (which won't be discussed) and (2) to check some transaction values to ensure that they make sense. For the latter purpose, MAX_MONEY is used in the inline function called MoneyRange() in the "main.h" file:

Code:

inline bool MoneyRange(int64 nValue) { return (nValue >= 0 && nValue <= MAX_MONEY); }

This function simply checks to ensure that a value is not negative and does not exceed MAX_MONEY. Nowhere in the 42 codebase is MAX_MONEY checked against a sum of the balances of all accounts, which would require the computationally expensive task of either (1) calculating every account balance in the block chain and then adding them up, or (2) summing the coinbase (money generating) transactions over all blocks. The running total of money supply is not explicitly kept in the block chain.

The MoneyRange() function is used a few times in the 42 code. An arbitrary example is checking the the sanity of a transaction, as in the CTransaction::CheckTransaction() function within "main.cpp":

Code:

if (!MoneyRange(nValueOut))
            return DoS(100, error("CTransaction::CheckTransaction() : txout total out of range"));

Nowhere in the code for 42 does is MoneyRange() used to validate the total money supply of 42.


Notes:

[1] http://coinmarketcap.com/
[2] My screen name, tx42, is unrelated to 42 coin.
[3] http://www.42coin.org/
[4] http://en.wikipedia.org/wiki/1/2_%2B_1/4_%2B_1/8_%2B_1/16_%2B_%E2%8B%AF

How do I find out for a coin what is the

• the current block number
• current average block time (or time to find latest block)
• the current difficulty
• the re-target block number
• the re-target difficulty

Any help is greatly appreciated!

I wish I could post this to the graincoin thread (https://bitcointalk.org/index.php?topic=361503.0), but I'm a newbie.

I bought 1 Million graincoin for a significant amount of $ and BTC and a recent blockchain fork/fix took my coin!

See the beginning of the graincoin problem here: https://bitcointalk.org/index.php?topic=361503.420

The graincoin address was 93vjdAw4GWL8Fe1HhVrKqL29jMCbf2q9od

Check the block explorer to see that the address is now missing:

http://coinblockchain.com/grain/address/93vjdAw4GWL8Fe1HhVrKqL29jMCbf2q9od

I need to contact the graincoin devs to sort this out. This was a significant chunk of coin bought at significant expense.

How can I contact the devs in this situation. Can a non-newbie mediate a post for me?