I'm wanting to gauge what people are thinking about smart contracts. I know a lot of people don't like Solidity, but if you had a magic box that could support any programming language for smart contracts, what language would you choose and why?

I've reported a particular user (don't worry they'll chime in soon) for repeatedly posting 2 posts at a time, over 5 times now. Nothing I can tell has happened other than that the mod who handles it has found my complaint "accurate". Is this rule enforced or not?

Supcoin



Release Date

Feb 19th, 10pm EST. Check the altcoin calendar for easy conversion to your own time zone.

https://www.altcoincalendar.info/coins/1340-SUP (note, might take a couple hours before it's active)

Wallets and a CPU miner will be provided a day early, but will be put into a state so that it won't sync until the launch happens (ie, checkpoint with blocks being kept secret until release). This method worked very well for my last coin release, Fractalcoin, and makes launching a trivial activity as all that must be done is a node brought online.

There will be no warm-up period and it will be full rewards starting from block 16. (up until block 16 will be premined, block 1 is 1,000 coins, 2-16 is 0 reward to ensure integrity of checkpoint security for launching)

Downloads

Note: These wallets will NOT sync until launch time. This is intentional. At launch time, they will sync automatically and you can start mining

Binary wallets:
Supcoin 1.0.1 Linux 32bit
Supcoin 1.0.1 Linux 64bit
Supcoin 1.0.1 Windows 32bit Standalone
Supcoin 1.0.1 Windows 64bit Standalone
Supcoin 1.0.1 Windows 32bit Installer
Supcoin 1.0.1 Windows 64bit Installer
Supcoin 1.0.1 Mac OSX 64bit standalone
Supcoin 1.0.1 Mac OSX 64bit DMG/installer
Supcoin 1.0.1 Gitian Signatures (earlz)

Source code:
Supcoin 1.0.0 Source Code
Github

Miners:
PLUCK cpuminer
cpuminer signature (Wolf0)
PLUCK cpuminer source

NOTE: GPU miners require Computer 3.0 or higher! (was 3.5, but it's been updated)
PLUCK Nvidia GPU Miner (source)
Nvidia GPU Miner (Windows)
See this post for how to run it: https://bitcointalk.org/index.php?topic=950084.msg10518296#msg10518296

AMD sgminer with PLUCK support (windows)
AMD sgminer with PLUCK support (source)

Alternatively, you can also rent a miner at Betarigs: https://www.betarigs.com/list?miner_type=10

NOTE: If you compile the CPU miner yourself, make sure to use `make CFLAGS="-O3 -march=native"` otherwise, you'll end up wiht an unoptimized miner

Mining

Mining pools:

• https://sup.coin-miners.info
• http://sup.hardcoreminers.com/
• http://sup.maxminers.net

How to solo-mine:
You can use the built-in miner by clicking on the Tools menu, and then click on Debug Window. At the debug console, type in "setgenerate true -1"
However, the built-in miner is much slower than the standalone miner. To solo-mine to your local wallet, first put a file named "supcoin.conf" in the proper directory(usually inside either your home directory/.supcoin or under %APPDATA%) Put these contents in it:

Code:

rpcuser=<SOME USERNAME>
rpcpassword=<SOME PASSWORD>
server=1

And then make a batch file (or similar shell script) with these contents under the same directory as the cpuminer:

Code:

wolf-pluckminer-generic64.exe -o http://127.0.0.1:4412 -O <USERNAME>:<PASSWORD>

Make sure to replace all the appropriate things with appropriate content

NOTE: If you'd like to test things out, you can use testnet. Start the wallet with the "-testnet" command line argument, and change your miner to use an appropriate testnet address and 127.0.0.1:14412 as the URL

For pool operators:

Please make sure to use the Scrypt difficulty divider adjustment for pool shares!

NOMP multi-hashing module with PLUCK support: https://github.com/ocminer/node-multi-hashing
Python PLUCK module: https://github.com/ocminer/pluck-python-hash

Premise

Hello,

I've been working on a big coin for the past month, and it's been on my mind for over a year now with all the ideas for it finally having a solid solution and plan to accomplish it. Sadly, Supcoin is not that coin. Basically, I need a coin to test some things, and that is this coin! I'm not ready to discuss my big coin project just yet (there will be a pre-ann in a couple months), but this coin is my way of making sure that the codebase I'm using is good.

Features:

• C'mon, you've always wanted to greet someone by giving them some SUP
• Based on bitcoin 0.10 (includes headers-first, which significnalty speeds up syncing times)
• 5 minute blocks
• Block reward halves every 100 days, starting at 10 coins per block
• PLUCK, memory hard hashing algorithm based on SHA256, using 128Kb of memory
• Digishield difficulty adjustment
• addrindex support (use -addrindex to the daemon and you can use RPC calls to query the balance of addresses on the blockchain)
• OP_CHECKLOCKTIMEVERIFY support, for advanced timelock contracts (from Viacoin)
• All BIPS enabled, including BIP66
• Traditional pure PoW
• Reasonably small premine of 100 blocks worth, with bounties
• First of it's kind Proof Of Permission: Whitepaper

Premine breakdown: (1,000 SUP)

• CLAIMED 50 SUP for me, to do whatever with(ie, to sell)
• CLAIMED 350 SUP for a PLUCK Nvidia GPU miner
• 300 SUP for a PLUCK AMD GPU miner
• CLAIMED 50 SUP for a NOMP module compatible with PLUCK(including pull requests and acceptance into the project)
• 200 SUP for someone who can takeover this coin with a real marketing plan, etc
• CLAIMED 50 SUP for whoever can make a decent logo (see below)

PLUCK:

PLUCK is a configurable hashing algorithm using SHA256. I developed PLUCK because most algorithms are not actually memory hard. They are constructed in such a way that many things can be chosen to not be stored into memory and can instead be recalculated. PLUCK does not suffer from this exploit. See also this article for more explanation.

This is similar to a merkelhash in a way, but is specifically designed for PoW to not allow breaking the memory hardness requirement. ASICs will always be possible, but would require expensive and large memory caches that can not be optimized away in anyway.

The core weakness in scrypt is that most variables stored in memory can easily be calculated more than once to save on memory costs. Although this is in theory less effecient, it ends up making ASICs and such faster by requiring less (expensive) cache memory.

This hashing algorithm is designed so that this can not take place. Recalculating anything stored in memory is as expensive as recalculating all the progress made thusfar on the hash. In the worst case, it may be possible reduce memory costs by 50% by recalculating the first half of the SHA256 hash values, but this would of course have extremely diminishing returns since this requires many SHA256 hashes to be computed.

Normally, I would scoff at the idea of writing my own hashing algorithm. However, I've taken precautions to ensure that this is at least as secure as sha256. Sha256 has a block input size of 512 bits, or 64 bytes. In ALL hashes generated, at least 256 bits of this input consists of an unmodified SHA256 hash generated previously. This ensures that the algorithm carries over SHA256's collision resistance and preimaging protection. Because of this property, I feel it is a safe cryptographic hash. The worst case is that the memory-hardness aspect is broken. The hash itself should never be broken (ie, collisions or preimages) unless SHA256 is broken in some way.

Supcoin

So, I'm a pretty busy guy. I'm still working a lot on the coin that comes after this. However, I intend to do maintenance on Supcoin at least until that coin is released. Supcoin should ideally be trivial to maintain as I strive to write coins that don't need forks and such to fix things. However, any issues that come up I will fix. I will not be adding gimmicky features however. I might add some non-forking features eventually just to test them out on a live network, but I'm not making any promises on that.

I will not do any kind of coin swap or anything like that when I release the next coin I'm working on, however, I might offer some kind of rewards for people that held some amount at some point in time, as an additional distribution mechanism.

Anyway, I'm a developer, not a marketer or community manager or anything like that. If you are someone who could do a "takeover" of the project, then have at it! I'll be holding onto 200 SUP to reward for a successful community takeover with a leader that proves they aren't just trying to do a pump and dump (ie, after some amount of time)

GPU MINER BOUNTY

CLAIMED -- final total given was 0.45 BTC

In order to raise tangible funds to motivate GPU miner devs, I am now hosting a donation address for Bitcoin.

1K6cUbtsn5xinD8XfjnTn7UnsMriLhZaGD

The first GPU miner to be created (AMD or Nvidia) and published under an open source license will receive all the money from this fund.

I'm putting in 0.25 BTC of my own money. I encourage everyone to donate what you can to help make this a lucrative bounty.

A new version of OpenSSL was released 2 days ago. This version of OpenSSL is more strict about what cryptographic signatures it is willing to accept. This can cause a blockchain fork if a specialized transaction with a non-rigid transaction is added to the blockchain, or if one is already on the blockchain. For more information, see gmaxwell's post about this issue http://sourceforge.net/p/bitcoin/mailman/message/33221963/

Again, DO NOT UPDATE TO OpenSSL 1.0.0p / 1.0.1k if you compile your own wallets. Windows wallets are not affected (but developers that compile altcoin wallets for Windows need to be aware of this)

If you're an altcoin developer, please merge in the two latest commits from the Bitcoin 0.8 branch: https://github.com/bitcoin/bitcoin/commits/0.8 (or 0.9 if your code is based on Bitcoin 0.9). This will fix the issue so that the latest OpenSSL will not cause a fork

To be specific (for most altcoins), you need to make these modifications to your code:

1. https://github.com/bitcoin/bitcoin/commit/f4134ee30100a3ba8a25e3f7ac6c4e0b39fb05a3
2. https://github.com/bitcoin/bitcoin/commit/91e1332011ca647362f95f34ae6c530640bfef98

This will make it so that the new OpenSSL doesn't cause a fork

The ADMT thread is moderated and I assume my post will get deleted immediately. So, I'm posting with a new topic.

Anyway, here is my review including the exploit. Summary is, the dev made a hidden premine of 20M or so, and hid it in such a way that not even traditional block explorers could reveal it

My review follows

Code:

adamantiumcoin https://bitcointalk.org/index.php?topic=829498.0

Heritage: HACK, DRM

Problems:

* CRITICAL: Reward for block 22 can be any amount that is desired
** The block explorer is compromised or the coin is serrepticious enough that it causes the block explorer to lie
** http://104.131.48.111:7200/block/00000283b17dbaa7445d64c988dcb7e58227ba49b686e029bbaf81bf67224993

review stopped at this point and early notice given to exchanges and miners.

Notes:

node:     {"108.170.2.13", "108.170.2.13"},

this is where the dev allows a block with non-standard reward to be mined
@@ -1582,7 +1583,7 @@ bool CBlock::ConnectBlock(CTxDB& txdb, CBlockIndex* pindex, bool fJustCheck)
     {
         int64_t nReward = GetProofOfWorkReward(nFees);
         // Check coinbase reward
-        if (vtx[0].GetValueOut() > nReward)
+        if (vtx[0].GetValueOut() > nReward && pindexBest->nHeight+1!=22)
             return DoS(50, error("ConnectBlock() : coinbase reward exceeded (actual=%"PRId64" vs calculated=%"PRId64")",
                    vtx[0].GetValueOut(),
                    nReward));

a variable used
@@ -330,6 +332,7 @@ bool CTransaction::IsStandard() const
 // expensive-to-check-upon-redemption script like:
 //   DUP CHECKSIG DROP ... repeated 100 times... OP_1
 //
+int64_t nvout=2000000000000000;

here is where the dev hides the amount in supply for RPC calls
@@ -1618,6 +1620,10 @@ bool CBlock::ConnectBlock(CTxDB& txdb, CBlockIndex* pindex, bool fJustCheck)
 
     // Update block index on disk without changing it in memory.
     // The memory index structure will be changed after the db commits.
+    if(pindexBest->nHeight+1 == 22) {
+    pindex->nMint = nValueOut - nValueIn + nFees - nvout;
+    pindex->nMoneySupply = (pindex->pprev? pindex->pprev->nMoneySupply : 0) + nValueOut - nValueIn - nvout;
+    }  

here is where he hides the amount mined with the generation transaction causing both my own block explorer, and Abe to report it wrongly
+++ b/rpcrawtransaction.cpp
@@ -74,7 +74,12 @@ void TxToJSON(const CTransaction& tx, const uint256 hashBlock, Object& entry)
     {
         const CTxOut& txout = tx.vout[i];
         Object out;
+        if(tx.GetHash().GetHex() == "f48435e7305419f3fb4db67de5eca21bdd92a44babe7f056dfbeb1b7600d4c4e") {
+            out.push_back(Pair("value",0.00000000));
+        }
+        else {
         out.push_back(Pair("value", ValueFromAmount(txout.nValue)));
+    }

Here is block 22 when these transaction hiding bits are removed:
[earlz@li67-111 src]$ ./AdamantiumCoind getblockbynumber 22 true
{
    "hash" : "00000283b17dbaa7445d64c988dcb7e58227ba49b686e029bbaf81bf67224993",
    "confirmations" : 596,
    "size" : 175,
    "height" : 22,
    "version" : 6,
    "merkleroot" : "f48435e7305419f3fb4db67de5eca21bdd92a44babe7f056dfbeb1b7600d4c4e",
    "mint" : 0.00000000,
    "time" : 1413949218,
    "nonce" : 7462376,
    "bits" : "1e02bf73",
    "difficulty" : 0.00142155,
    "blocktrust" : "5d29ee",
    "chaintrust" : "3b4a09d",
    "previousblockhash" : "000001f2f69d68be7ec69dd877f801963a823bf31691d69c5180c564d9d21d2f",
    "nextblockhash" : "000000bc54ac049a0c01fd2d3be098b08247bc16df20f1101a9b631a85f7f2fa",
    "flags" : "proof-of-work",
    "proofhash" : "00000283b17dbaa7445d64c988dcb7e58227ba49b686e029bbaf81bf67224993",
    "entropybit" : 1,
    "modifier" : "00000000001cb4ed",
    "modifierchecksum" : "8cbc4017",
    "tx" : [
        {
            "txid" : "f48435e7305419f3fb4db67de5eca21bdd92a44babe7f056dfbeb1b7600d4c4e",
            "txid" : "f48435e7305419f3fb4db67de5eca21bdd92a44babe7f056dfbeb1b7600d4c4e",
            "version" : 1,
            "time" : 1413949218,
            "locktime" : 0,
            "vin" : [
                {
                    "coinbase" : "01160101",
                    "sequence" : 4294967295
                }
            ],
            "vout" : [
                {
                    "value" : 20000000.00000000,
                    "n" : 0,
                    "scriptPubKey" : {
                        "asm" : "OP_DUP OP_HASH160 e829b472157a48cf939a76e66ac710c8d3898d95 OP_EQUALVERIFY OP_CHECKSIG",
                        "reqSigs" : 1,
                        "type" : "pubkeyhash",
                        "addresses" : [
                            "AcwSNi1VZ41WLErCguXiTh9d9Q9CjEQ1rB"
                        ]
                    }
                }
            ]
        }
    ]
}



Watermarks: uint64_t, pos, drm-like

Btw, if anyone would like to request a code review. I try to review popular and new coins automatically. However, if you want to request a coin reviewed quickly (24-72 hours), you can PM me. I require a modest payment though to skip the line since my time is at a premium.

So, I've seen a number of really horrible ways people have use to "destroy" coins. First off, YOU DO NOT NEED TO SEND YOUR COINS TO ANYONE TO DESTROY THEM. You can destory coins without having to trust anyone

All you need to do is send the coins you wish to destroy to a special provably unspendable address. Specifically, I generated the addresses such that it would require you to generate a public key which when hashed in various ways hashes to 20 bytes of 0.. This is of course statistically impossible unless sha256 or ripemd160 has fatal flaws in it.

Anyway, I've generated a rather large list of addresses. You must generate the address for each different altcoin depending on the "version" of it's address. I include easy instructions on how to properly match up your coin to the proper burn address.

It was a lot of text, so I put it on my blog http://earlz.net/view/2014/10/22/0340/provably-spendable-altcoin-burn-addresses

Also see the PGP signed version here: https://gist.githubusercontent.com/Earlz/de3cc5f6ee85c7a69d53/raw/e9b8f53ddadd1677fc2fd2a0f1df8547e08ae408/gistfile1.txt

For reference to what it looks like on blockchain, you can look at the burned glowcoin transaction: http://cryptobe.com/tx/429d486e39921b0f5dce8b5905afeed4332605aad2d8a5beb244ab2bbb69479a

Also, if you like what I do and all that, donate to me at 1J5t3CW3PZd3YxJZDtuvkijAgHX1MrahiD

DOGE VERY DOGE SUCH VERY COIN DOGE PREANNOUNCEMENT DOGE SOON COMING DOGE




DOGE SPECS DOGE

DOGE IS MORE MUCH DOGE



DOGE MEME = 1 DOGE = VERY PROFIT DOGE

DOGECOIN

DARK

DOGE





VERY COMING DOGE SOON

So, it's possible to "perfectly" hide a premine. I won't go into the deep details of how this is done, since I don't want to make it easy for these scam devs. However, when it's perfectly hidden, it's impossible to go back with a block explorer and spot it. The timestamps on the blocks are lies to just look like it was mined after launch.

Anyway, this is a call out for early miners. You know who you are, the people with email subscriptions to the announcement forum that kick on miners with ninja launches and such. Also this applies to pools that pre-register and such.

The only way to spot these perfectly hidden premines is to have a node on the chain at the very beginning after launch. A semi-smart scammer will wait before broadcasting the premine blocks, so that shadow_runner and people like him that post the block counts when they get it downloaded will show that only 10 blocks or some such has been mined. You can tell that a hidden premine is broadcast later by a very large chain of orphan blocks. For instance, if you mine for 2 minutes and get 80 blocks, and then your chain is orphaned by another chain with 90 blocks (or even 70 blocks, but with more cummulative difficulty) then there is a good chance that this is a hidden premine.

If you encounter a huge orphan chain at launch a minute or two after mining, please save your debug.log! It's the only thing that records the info that can make this kind of behavior spottable. You can then post this info for analysis by me and others.

Of course, orphan chains at launch are quite common. What we're looking for though is huge orphanings.  Particularly if you mined a very early block, like block 10, and then mine until block 60 and it's later orphaned all the way back to 9, this indicates that someone was not listening to the block you broadcast. Just because you encounter orphans at launch does not mean there is a hidden premine, it only indicates that it's possible. Analysis will be needed to determine it, and even then nothing is 100% certain.

If you encounter huge orphan chains, please save your debug.log. Post it publicly if you can and PM me.

Bitchcoin! Featuring Bitching about premines, bitching about unsyncing wallets, and bitching about the unfair launch process.



You download it now and can run the wallet and all, but it won't sync because of a checkpoint. At some random time in the next 3 days I'll send the required checkpointed blocks to the nodes and mining will begin pretty much instantly.

Want to mine this shit? Check out this subreddit post for pools. Apparently bitcointalk doesn't allow pools to tell people that you can mine somewhere, so submit a comment there. Don't PM me pool info, cause I won't add it to this topic. Ain't nobody got time for that.

Also, don't expect me to ever update this again. This coin was just cause I wanted to have some fun and run a few tests that can only really be done with a new coin. However, I would really love if people fork a coin like this, rather than the shitcoin bitcoin 0.8 stuff.

Download the wallets to start bitching!

windows
github
mac (if you compile it for me, I won't reward you, but I'll put a link here)

Bitchcoin specs:
RPC 6111
P2P 6112
20 BTCH per block for 1st month. Then drops to 10 BTCH
Every 10K blocks, there is a bitch block with no reward
no premine
X11 because it's the one people bitch the least about and I already had a coin with X11 so it was easy
First "fair ninja"
No addnode shit needed
720 block maturation time. (3 days), to ensure people bitch about not being able to dump

I repeat THIS WILL NOT SYNC UNTIL LAUNCH

Bitsta deleted my post linking to my negative coin review, so I made this unmoderated thread.

My review in full is here: https://github.com/Earlz/coinreviews/blob/master/rootcoin.txt

First topic of discussion can be the purposeful instamine. Basically, the difficulty adjustment is changed so that the first 450 blocks were minimum difficulty, meaning they got mined extremely quickly.

Second topic can be the actual premining of about 115 blocks. You can verify this yourself by checking the timestamps on blocks 2-115 using ssdpools(terrible) block explorer, or checking using the debug window, and comparing to when he announced the launch of the coin (August 23, 2014, 01:09:49 AM UTC).

For reference, me and bitsta talked a bit in #bittrex IRC about it. If you'd like to see his side as well: http://pastebin.com/2zrfGH3J

Hello,

I just wanted to alert people to some stuff I've been doing for a while, but just now is being made public. I code review coins. Some of the reviews are requested, some I do on my own.

For reference, I only analyze the source code, it matching the ANN, and sometimes the blockchain with a local or remote block explorer. I do not analyze binary wallets, nor try to evaluate how trust worthy a developer is (though I sometimes point out when a developer is especially good or bad)

You can see my listing of reviews on Github.

Note, all of the reviews are best effort and not at all guaranteed to be exploit free. I only try to find the more obvious exploits.

My old thread was moved to the marketplace and is here. I'm not trying to really sell this as a service, and would like continual discussion around my reviews (think I am wrong about something? Tell me!) and generally I am looking to ensure coins with critical bugs or exploits are called out on it.

Hello,

I just wanted to alert people to some stuff I've been doing for a while, but just now is being made public. I code review coins. Some of the reviews are requested, some I do on my own.

For reference, I only analyze the source code, it matching the ANN, and sometimes the blockchain with a local or remote block explorer. I do not analyze binary wallets, nor try to evaluate how trust worthy a developer is (though I sometimes point out when a developer is especially incompetent or competent for the LOLs)

You can see my listing of reviews on Github.

If you'd like to request me to review a coin's code, you can PM me here, or contact me on freenode IRC as `earlz`. Note I only have so much time for these, so it'll be rare that I'll do one without some kind of payment. (and no, 0.01 BTC is not rich enough for me )

Note, all of the reviews are best effort and not at all guaranteed to be exploit free. I only try to find the more obvious exploits.

Also, my last review was Hertzcoin, which had critical exploits. So, since the Hertzcoin developer locked the thread, I couldn't elaborate more on the exploit he used. Basically, he made it so that a block of any difficulty would be accepted by the network, regardless of the current network difficulty. This meant they could easily double spend anything they wanted (because a 51% attack is trivial with a single computer) and they could mine as many blocks as they wanted. Just wanted to include that tidbit somewhere

I just wanted to give a quick FYI to all the coin devs and future coin devs.

When you use "0.2*COIN" to represent 0.2 coins, it is not safe. Floating point values in C++ are not guaranteed to be exact, and they are not guaranteed to be consistent across platforms or even compilers. Please stop doing this. For more information, see this stackoverflow question.

The proper way to represent a division of coins is to either represent it as satoshis (ie, without COIN), or to use only integers, such as "2*COIN/10" to represent 0.2 coins.

This WILL cause forks and bad wallets on non-x86 architectures, such as the raspberry pi and many others and is in general a very bad practice.

I'm trying to modify how change addresses work in Bitcoin 0.9 and desire to change the code (wallet.cpp:1399) so that instead of sending change from a transaction to a new key, it will send  it back to one of the addresses that was used as an input. The only thing I have access to in this area though is a list of CTxIns. I see no clear way of deriving a bitcoin address though from a CTxIn. There are things like the script used for the input, but I see no clear cut way of seeing the address the CTxIn is associated with

Can anyone give me a hint as to how to do this?

My best guess was to use a previous vout CScript from one of the CTxIn inputs, but this would cause problems when using non-standard transactions to send funds, and causes peculiar scripts from solomined transactions. 

[Megcoin 200M give away]

Megcoin 200M give away

As part of our rebranding we will be giving away a total of 200 million (400 blocks worth) of Megcoin to our users and to encourage new comers to join us.To qualify and make the distribution more fair we have set tasks to complete in order to obtain a chunk of the give away fund. These tasks are intended to help advance the coin whilst also giving something back to the users.

The structure of the give away is as follows:

Community giveaway (50 Million):

• 50K Meg - Tweet your Megcoin address along with #megcoin using an account with 10 or more followers.
• 50K Meg - Comment on the give away thread of our subreddit and subscribe using an account 1 week or older.
• 50K Meg - Liking and commenting on the Megcoin facebook page.
• 50K Meg - Joining our IRC channel and saying hello (#megcoin).
• 200K Meg - Making a Youtube video discussing Megcoin.

Infrastructure advancement (150 Million):

• 25M Meg - Informative Youtube video describing Megcoin suitable for the Megcoin home page.
• 25M Meg- Contributing a better looking website design.
• 50M Meg - First established merchant to accept Megcoin.
• 1M Meg - Service using Megcoin (such as dicegame, faucet, etc) up to 10M.
• 20M Meg- Mac OSX wallet.
• 20M Meg - Ubuntu wallet package for Ubuntu 12 and 14 LTS.

Note, do NOT post your address on this thread. Posting addresses on a giveaway thread like this is strictly prohibited by bitcointalk and posting on this thread will not give you any benefits

[Most Extravagant Goat Coin [MEG]]

Most Extravagant Goat Coin [MEG]




Mandatory Update!

Planned Fork at block 18,000! Upgrading is MANDATORY!

Phase 1 – Rebranding and strategy
As many of you will be aware the Megcoin team decided to alter our strategy for Megcoin. The first phase of this strategy was detailed in the re-announcement which saw the coin rebranded and a team formed to advance the coin.

This was successful and as such we succeeded in getting Megcoin listed on Bittrex

Phase 2 – Block reward and fees
The second phase of our strategy focuses on the specifications of the coin. This will involve improvements to the block reward schedule and the transaction fees.

The planned changes are listed below and will be implemented by a fork at block 18,000:

New block reward schedule:

• 18,000–200,000: 50K Megcoin
• 200,001–400,000: 25K Megcoin
• 400,001–600,000: 12.5K Megcoin
• 600,001–800,000: 6250 Megcoin
• 800,001–1,000,000: 3125 Megcoin
• 1,000,000+: 10 Megcoin

Transaction fee structure:
A typical transaction will now have 1 Megcoin + 0.5% transaction fee to replace the present transaction fee of about 1 Megcoin per transaction. After May 17th, transactions without proper fees will not be accepted by nodes.

Why this benefits Megcoin:

• The percentage fee will be used as an incentive to mine and enhance the security of our network, despite decreased reward payouts
• The implementation of the percentage fee will also enable the redistribution of wealth accumulated from launch to new users to ensure that the coin is both sustainable and attractive to these new users.

These changes will take effect after block 18,000 and upgrade is MANDATORY.

The updated wallets are listed below

About

Megcoin is a revolutionary new cryptocurrency sporting a new algorithm (SCRYPT-N-R) and building upon the strengths of the Bitcoin 0.9 wallet to create a very fast and strong coin. Unlike most other  new coins Megcoin is immune to the recent influx of standard Scrypt ASICs and has taken steps to ensure that ASICs will not pose a threat therefore making it an excellent choice for both CPU and GPU miners. Megcoin has a strong development team pushing the advancement of the coin on all fronts and as such is positioned to become a major cryptocurrency. It has not been premined and is fully featured with multiple geographically-diverse DNS seed nodes to ensure extremely fast wallet synchronizations.

Rebrand and Reannouncement

The rebrand and reannouncement of this coin is due to the formation of a strong marketing and development team which was not present at launch. After its formation our team decided that in order to become a key player and strong force in cryptocurrency we needed to create a stronger strategy for success and part of this was rebranding to create a distinct image and plan going forward.

On behalf of the Megcoin team we would like to thank you for your patience with our coin through these changes. We believe that these changes are ultimately for the best and are essential if we are to push this coin to the next level. We urge you to not miss out on this opportunity to be a part of our coins journey.

Note: All previously mined coins remain unchanged as the changes are only related to branding and strategy.

Rebranding Giveaway!

In order to redistribute wealth with the rebranding, we are having a 200M MEG giveaway! See this thread for details!

Most Extravagant Goat?

Meet Meg, our coin mascot. A friendly extravagant goat who is the face of our coin and movement. Meg bought all of his gold bling with his Megcoin wealth but still remains excited for what's coming next. Join Meg!

Specifications:

• Launched May 3rd, 2014 - Original Announcement
• PoW Algo: Scrypt-8-4 (scrypt-n-r)
• Premine: 0%
• Total: Infinite (20K final block reward)
• Block time: 60 seconds
• Reward halved: Every 200,000 blocks
• Rewards mature: 120 blocks (~2 hours)
• Difficulty adjustment: Every block (Digishield)
• Wallet forked from Bitcoin 0.9

What is Scrypt-N-R and how does it make Megcoin superior?

Megcoin's algorithm uses a new algorithm dubbed scrypt-N-R. Typically, scrypt means scrypt with N=1024, R=1, P=1. This algorithm changes R for more granular tuning of memory usage. Currently, there is only the wallet miner and cpuminer(minerd) ported to the new algorithm. The memory usage of scrypt-8-4 is only 4Kbytes, compared to normal scrypt where it is 128Kbytes.

Scrypt-R-N ASICs are not practical to make for Megcoin because of the short "payout streak" period of around 1.5 years. If ASICs were produced for the new algorithm it would be near the end of the large block rewards when mining is needed more for network stability rather than for coin generation.

Security provided by Digishield

Megcoin uses the Digishield difficulty algorithm which has been proven stable and effective on Dogecoin and Digibyte. Although multipools shouldn't pose a threat due to our unique algorithm parameters, Digishield has been proven to handle large hashrate changes very well to ensure that the network is never stuck with slow blocks or vulnerable to a timewarp attack.

Advanced wallet building upon Bitcoin 0.9

Unlike many other new Scrypt altcoins Megcoin has decided to base our wallet on Bitcoin 0.9 which we forked to produce Megcoin's wallet. This decision was taken to ensure that the Megcoin wallet included many of the advancements that Bitcoin 0.9 has along with some of our own:

• A faster graphical user interface (supporting Qt5 as well).
• Fixes for transaction malleability.
• Services separated into megcoind, megcoin-cli and megcoin-qt.
• Many more features which can be seen in the bitcoin 0.9 changelog

Wallet download

• Windows Wallet (32 bit)
• Mac OSX
• Linux wallet coming soon .

The source code is available on Github for self-compilation and review.

Mining

Mining Megcoin couldn't be easier, get started with out CPU miner below:

• CPUMiner - Windows x64 build
• The wallet supports solo mining using "setgenerate true -1"

See also an easy getting started guide here.

Pools

Megcoin is currently supported by these trusted pools, more will follow:

• http://coins.rapidhash.net
• http://megpool.mooo.com
• http://megpoolzws.com

Reward schedule:

• 1–200,000: 500K Megcoin
• 200,001–400,000: 250K Megcoin
• 400,001–600,000: 125K Megcoin
• 600,001–800,000: 62500 Megcoin
• 800,001–1,000,000: 31,250 Megcoin
• 1,000,000+: 20,000 Megcoin

Community and Resources

Come and get involved in our Megcoin communities, we look forward to hearing from you:

• Reddit
• Twitter
• Facebook
• Website
• IRC/Freenode: #megcoin

Exchanges

• Bittrex
• We are working to get Megcoin onto Mintpal and Cryptsy along with as many other exchanges as possible, this is a key and urgent priority of our team.

Block explorers

• http://cryptexplorer.com/chain/Megcoin
• http://megchain.earlz.net:8080

Merchandise

• http://www.cafepress.com/megcoin

Services

We understand that gaining widespread adoption and success for our coin will rely strongly on the production of new services which utilise Megcoin. At present we have an IRC tipbot for Megcoin (megtip) which you can use in your channel upon request. We will be pushing strongly for more services in the future and welcome any developer who would like to use Megcoin to get in contact with our devteam.

Testnet

If you would like to test services or mining with Megcoin we have testnet nodes running meaning that syncing should be effortless. If you would like more details then please contact our team.

Nodes

There are multiple geographically-diverse DNS seeds built into the wallet ensuring that the wallet will sync very quickly. If you have a reliable node and would like to help strenghten the Megcoin network then please contact us and we will add it to the node list. Please note that no addnode arguments should be required right now.


Bounties

• AMD GPU Miner - 130 Million MEG (Bounty address: MSGoyrBfXad1Pv8Jqc3t74a2yBsDoDbE1G
• Nvidia GPU Miner - 4 Million MEG
• Informative youtube video suitable of the homepage - 25 Million MEG
• Established merchant to accept Megcoin - 50 Million MEG
• Service using Megcoin, such as faucet, dice game, etc - 1 Million MEG (rewarded up to 10 times)
• Ubuntu wallet package - 20 Million MEG

Credits

Please consider supporting the artist of our logo by donating Dogecoin here: DC1ZEaQMuQfgcYvtd6DhJ6k4Y8ogk9VKYy

There is a mining pool I'm trying to link to in a coin ANN post and I can't. For reference, not all links are filtered though:

[Suspicious link removed]/ m e g . p o o l z . w s
http://earlz.net e a r l z . n e t
http://coins.rapidhash.net c o i n s . r a p i d h a s h . n e t

Why is this?

This is left here only for archival purposes. Please go to the new announcement for discussion: https://bitcointalk.org/index.php?topic=603892

Megcoin - Get Megged [MEG]




Specifications:

• PoW Algo: Scrypt-8-4 (scrypt-n-r)
• Premine: 0%
• Total: infinite (20K final block reward)
• Block time: one minute
• Reward halved: every 200,000 blocks
• Rewards mature: 120 blocks (~2 hours)
• Difficulty adjustment: Every block, digishield
• Wallet forked from Dogecoin 1.7/Bitcoin 0.9

Reward schedule:

• 1–200,000: 500K Megcoin
• 200,001–400,000: 250K Megcoin
• 400,001–600,000: 125K Megcoin
• 600,001–800,000: 62500 Megcoin
• 800,001–1,000,000: 31,250 Megcoin
• 1,000,000+: 20,000 Megcoin

Scrypt-N-R

Megcoin's algorithm uses a new algorithm I've dubbed scrypt-N-R. Typically, `scrypt` means scrypt with N=1024, R=1, P=1. This algorithm changes R for more granular tuning of memory usage. Currently, there is only the wallet miner and cpuminer(minerd) ported to the new algorithm. The memory usage of scrypt-8-4 is only 4Kbytes, compared to normal scrypt where it is 128Kbytes. This means that GPUs and FPGAs will have a large advantage once they are ported to the algorithm. However, ASICs are not practical to make for Megcoin because of the short "primary mining" period of about 1.5 years. If ASICs were produced for the algorithm, it would be near the end of big rewards and when mining is needed more for network stability than for coin generation.

Digishield

This uses the Digishield difficulty algorithm which has been proven stable by Dogecoin. Although multipools shouldn't be a worry with the unique algorithm parameters, digishield has been proven to handle large hashrate changes very well.

Forked from Dogecoin 1.7/Bitcoin 0.9

Because it was forked from Dogecoin 1.7, which is forked from Bitcoin 0.9, Megcoin's wallet includes the many advancements that Bitcoin 0.9 has:

• A faster graphical user interface (supporting Qt5 as well)
• Fixes for transaction malleability
• Services broken up into megcoind, megcoin-cli, and megcoin-qt
• Many more features which can be seen in the bitcoin 0.9 changelog

Downloads

• windows (32bit)
• Mac OSX wallet coming soon

The source code is available on github for compiling on Linux and elsewhere

Resources

• reddit
• Join the IRC channel #megcoin at freenode. I have a tipping bot and not afraid to use it :)
• website

Block explorers

megchain.earlz.net:8080
cryptexplorer

Mining

• cpuminer for mining with pools (stratum support) 64bit windows build
• The wallet supports mining by using `setgenerate true -1`

This should be very easily (and effeciently) mined by GPUs and even FPGAs due to it's low 4Kbyte memory requirement. I do not have the knowledge to port a GPU miner though, so this is why I've only ported cpuminer.

Pools

Due to some weird filtering by [Suspicious link removed]ee http://megcoin.com for a full list of pools

• Rapidhash

[Suspicious link removed][/url] PROP, 1% fee[/li]
[/list]

I'm running a semi-private pool (because I don't have the expertise to run a pool reliably) that you can join into if you want. However, right now I recommend setting up p2pools or solomining because like I said, I am not an expert pool runner and I'd hate to lose people's coins

Pools will be listed here as they are made.

Nodes

I've tried to ensure there are plenty of servers for the initial rush of wallet syncs including nodes in the US, Europe, and Japan. However if you have a reliable node, report it to me and I'll add it to this list in case those servers get overloaded or are later scaled down for cost reasons. No addnode arguments should be required right now.

Exchanges

https://www.bittrex.com/Market/?MarketName=BTC-MEG

Bounties

• AMD GPU miner 130M MEG!. Bounty wallet is MSGoyrBfXad1Pv8Jqc3t74a2yBsDoDbE1G
• Nvidia GPU miner 3M MEG
• Mining pool 2M MEG claimed

Testnet

Also, if you would like to test services or mining with Megcoin, I have testnet nodes running so syncing should be trivial