Mark Friedenbach

Freicoin version 12.1.3-10161 is now available from: Linux 32-bit: https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-linux32.zip Linux 64-bit: https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-linux64.zip macOS (app): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-osx.dmg macOS (server): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-osx64.tar.gz Windows 32-bit (installer): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-win32-setup.exe Windows 32-bit (zip): https://s3.amazona

A few months ago I was working on the donation matching code in order to perform an audited final payment. In the process I was consolidating funds from the 320 cold-storage foundation addresses into a single master key that has never been on a computer connected to the internet. No funds have been destroyed, except those lost to demurrage as part of the consolidation. I don't have the address for this key on hand wihle typing this, but it shouldn't be hard to work out -- I believe it's currently the highest value address on the chain, and you can find it simply enough by following the foundat

What about it?

I don't know if there's a paper or anything looking at that. It is more a statement of our experience competing with other SHA-256 coins, and the bitcoin cash ecosystem experiencing exactly the same thing a number of years later. This sort of discussion should probably happen on the GitHub issue.

Yes it is a blocker for forward blocks (meaning: forward blocks depends on this being finished) because the difficulty adjustment algorithm can only be changed as a soft-fork simultaneously with deployment of forward blocks.

Skaro, maybe you could help out on the following issue, a blocker for deploying forward blocks? https://github.com/tradecraftio/tradecraft/issues/3 If so, I could provide a bit more detail about my current thinking in regards to that.

Freicoin version 12.1.2-10135 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new point release, enabling soft-fork deployment of a collection of time-lock related protocol features. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues How to Upgrade If you are running an older version, shut it down. Wait until it h

For transparency's sake, here is the current listing of charitable organizations and the donations + matched funds that are owed to them: 'Abundant Currency Project', 29 (rejected) Donation: 0.00000000 Matched: 0.00000000 Payout: 0.00000000 Todo: 0.00000000 'Community Forge', 17 (validated) Donation: 1,996.60765506 Matched: 1,996.60765506 Payout: 1,096.20734614 Todo: 2,897.00796398 'Complementary Currency Resource Center', 28 (validated) Donation: 1,000.00000000 Matched: 1,000.00000000 Payout: 1,099.54585847 Todo: 900.45414153 'Cooperativa Integ

Freicoin version 12.1.1-10130 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new bug fix release, fixing an erroneous report of unexpected version / possible versionbits upgrade on all platforms. Upgrading to this release is recommended but not required. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues How to Upgrade If you ar

Freicoin version 12.1-10123 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new major version release, bringing sequence locks and lock-time soft-fork, new features, and other improvements. Please report bugs using the issue tracker at github. Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut

Freicoin version 11.3-8698 is now available from: * Linux 32-bit * Linux 64-bit * macOS (app) * macOS (server) * Windows 32-bit (installer) * Windows 32-bit (zip) * Windows 64-bit (installer) * Windows 64-bit (zip) * Source This is a new major version release, bringing both new features and bug fixes. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely s

Freicoin version 10.4.2 is now available from: * Linux 32-bit * Linux 64-bit * macOS (app) * macOS (server) * Windows 32-bit (installer) * Windows 32-bit (zip) * Windows 64-bit (installer) * Windows 64-bit (zip) * Source This is a new bug fix release, adding support for pool software that rely on freicoind for the correct coinbase commitments, including median time past. Upgrading to this release is required for miners which use pool software that depends on the availability of the "locktime" field from 'getblocktemplate,' but otherwise it is not req

Freicoin version 10.4.1 is now available from: * Linux 32-bit * Linux 64-bit * macOS (app) * macOS (server) * Windows 32-bit (installer) * Windows 32-bit (zip) * Windows 64-bit (installer) * Windows 64-bit (zip) * Source This is a new bug fix release, fixing an issue with incorrect display of immature and watch-only balances on all platforms. Upgrading to this release is recommended for those affected by this issue, but otherwise not required. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft

These are based off the release notes for the underlying bitcoin releases. Under "notable changes" the first two headings "Protocol-cleanup flag day fork" and "Depreciation of 32-bit clients" are new and specific to freicoin. Also note the entire notable changes section from the recently released v0.9.5.1-5869. The other stuff is shared with bitcoin. One of the big changes that came with 0.10 in bitcoin (which our v10 release is based off) was the introduction of watch-only addresses. I need this to do the final donation matching from the foundation funds.

Freicoin version 10.4 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new major version release, bringing both new features and bug fixes. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down

Freicoin version 0.9.5.1 is now available from: Linux 32-bit Linux 64-bit macOS Windows 32-bit (install) Windows 32-bit (zip) Windows 64-bit (install) Windows 64-bit (zip) Source This is a new minor version release, with the goal of backporting soft-fork activation rules for verification of the coinbase transaction's nLockTime field. There is also a modification of the wallet code to produce low-S signatures, and various bug fixes. Upgrading to this release is recommended. Please report bugs using the issue tracker at github: h

One of my nodes is getting a bunch of invalid transactions being sent to it: Given the fact that these transactions are off by only a few kria, it looks like someone is generating zero-fee transactions on a pre-fork wallet. Someone needs to update their wallet and make new transactions!

Look at the reference heights--they're the same. There's no demurrage if the reference height of the tx is the same as its inputs. Someone probably manually created these transactions. I'm not sure how ABE works to be honest. Just noticed that when you click on a transaction, the "Fee" field includes the demurrage. Maybe this is a long-standing bug in ABE I just didn't know about.

Well it looks like some work needs to be done to separate fee from demurrage in ABE explorer. But Freicoin integration should be much easier now.

I didn't realize demurrage was implemented inside of ABE. The RPCs report transaction values and demurrage a little bit more intelligently. Part of why I haven't made a new topic yet is I need to update the release notes to explain better how they work now. What it was doing before really didn't make any sense -- when looking at historical data it would show the transaction 'value' as the present adjusted value, and demurrage wasn't reported or worse it was part of the fee, etc. Now if you are using a certain wallet RPCs (getbalance with no arguments, listunspent) it will show the present

Yes and no, mostly no. “Sharding” is the term for splitting a single block chain into multiple chains sharing the same assets, which solves a latency problem fundamental to scaling and improves resistance to certain forms of adversarial attack. But a miner must still track all chains, or else forego the income involved. If we have so much activity across all the chains such that a single person cannot run a full node on ALL chains using the same PoW, then the whole system can no longer be decentralized. But things like efficient atomic swaps using adapter signatures, HTLC payment channel

Yup, pushed the code for the next release: v0.9.5.0-6. Everything seems good on my end.. just wanted to pull the release notes together for an official announcement. It's usable if you want to upgrade though. In fact, I'd highly recommend it as it comes with significant security updates. I've updated the download links on the main website for the gitian-built binaries. Also in the good news: macOS builds are back.

Edited first post in this topic to note the release of v0.8.6.2-5.

Sidechains and merge mining have their own intractable problems, and in particular they do not mix together very well (merge mining makes the sidechain problems worse, and vice versa). If freicoin were to be sidechain to another chain, it would have to either (1) be a separate proof of work, or (2) have all full nodes of both chains validate each other, an idea more commonly known as extension blocks. Setting freicoin up as a separately mined chain with a different proof of work (and therefore different hardware distribution) prepares for the first possibility while not excluding the second. B

Regarding ASIC reistance, it's a goal that in its strongest form is impossible. You cannot have an ASIC-reistant proof of work, and if someone is trying to tell you otherwise that's a good indicator you're dealing with a crank (or they're trying to sell you something). Anything you can do with a general application-agnostic circuit you can do more efficiently in a specialized circuit. This follows straight from information theory. HOWEVER, there is a weak form of ASIC-resistance which is interesting to note. With double-SHA256, GPUs are 100-1,000x more efficient than CPUs, FPGAs are 100-1