Another great release from ThomasV, SomberNight and BauerJ:  https://electrum.org/#download

# Release 3.1 - (March 5, 2018)

 * Memory-pool based fee estimation. Dynamic fees can target a desired
   depth in the memory pool. This feature is optional, and ETA-based
   estimates from Bitcoin Core are still available. Note that miners
   could exploit this feature, if they conspired and filled the memory
   pool with expensive transactions that never get mined. However,
   since the Electrum client already trusts an Electrum server with
   fee estimates, activating this feature does not introduce any new
   vulnerability. In addition, the client uses a hard threshold to
   protect itself from servers sending excessive fee estimates. In
   practice, ETA-based estimates have resulted in sticky fees, and
   caused many users to overpay for transactions. Advanced users tend
   to visit (and trust) websites that display memory-pool data in
   order to set their fees.
 * Capital gains: For each outgoing transaction, the difference
   between the acquisition and liquidation prices of outgoing coins is
   displayed in the wallet history. By default, historical exchange
   rates are used to compute acquisition and liquidation prices. These
   values can also be entered manually, in order to match the actual
   price realized by the user. The order of liquidation of coins is
   the natural order defined by the blockchain; this results in
   capital gain values that are invariant to changes in the set of
   addresses that are in the wallet. Any other ordering strategy (such
   as FIFO, LIFO) would result in capital gain values that depend on
   the presence of other addresses in the wallet.
 * Local transactions: Transactions can be saved in the wallet without
   being broadcast. The inputs of local transactions are considered as
   spent, and their change outputs can be re-used in subsequent
   transactions. This can be combined with cold storage, in order to
   create several transactions before broadcasting them. Outgoing
   transactions that have been removed from the memory pool are also
   saved in the wallet, and can be broadcast again.
 * Checkpoints: The initial download of a headers file was replaced
   with hardcoded checkpoints. The wallet uses one checkpoint per
   retargeting period. The headers for a retargeting period are
   downloaded only if transactions need to be verified in this period.
 * The 'privacy' and 'priority' coin selection policies have been
   merged into one. Previously, the 'privacy' policy has been unusable
   because it was was not prioritizing confirmed coins. The new policy
   is similar to 'privacy', except that it de-prioritizes addresses
   that have unconfirmed coins.
 * The 'Send' tab of the Qt GUI displays how transaction fees are
   computed from transaction size.
 * The wallet history can be filtered by time interval.
 * Replace-by-fee is enabled by default. Note that this might cause
   some issues with wallets that do not display RBF transactions until
   they are confirmed.
 * Watching-only wallets and hardware wallets can be encrypted.
 * Semi-automated crash reporting
 * The SSL checkbox option was removed from the GUI.
 * The Trezor T hardware wallet is now supported.
 * BIP84: native segwit p2wpkh scripts for bip39 seeds and hardware
   wallets can now be created when specifying a BIP84 derivation
   path. This is usable with Trezor and Ledger.
 * Windows: the binaries now include ZBar, and QR code scanning should work.
 * The Wallet Import Format (WIF) for private keys that was extended in 3.0
   is changed. Keys in the previous format can be imported, compatibility
   is maintained. Newly exported keys will be serialized as
   "script_type:original_wif_format_key".
 * BIP32 master keys for testnet once again have different version bytes than
   on mainnet. For the mainnet prefixes {x,y,Y,z,Z}|{pub,prv}, the
   corresponding testnet prefixes are   {t,u,U,v,V}|{pub,prv}.
   More details and exact version bytes are specified at:
   https://github.com/spesmilo/electrum-docs/blob/master/xpub_version_bytes.rst
   Note that due to this change, testnet wallet files created with previous
   versions of Electrum must be considered broken, and they need to be
   recreated from seed words.
 * A new version of the Electrum protocol is required by the client
   (version 1.2). Servers using older versions of the protocol will
   not be displayed in the GUI.

If anyone was looking for a break in the Bitcoin network to consolidate the small inputs in their wallet - this is a good time now!  https://bitcoinfees.earn.com/

You can send a transaction as low as 5 sat per Byte, and it should be included in the next block.   I just sent a 1kb transaction for $0.50 fees!

Roger Ver must have stop spamming the network to promote his BCH coin 

What is that new rule that we can't search throughout the website anymore?   We have to use google for that now?  WTF!

Like in 2015, someone just cloned the electrum.org website into electrum-wallet.com and distributes bad binaries.  

So far I found a few changes in their version of the installwizard.py file

Someone this morning got robbed with 45 Bitcoins from this trojan - ouch!!!   https://bitcointalk.org/index.php?topic=2059967.msg20555125#msg20555125

I used to be able to create .app and .dmg files from Source in v.1.9.x - but since v 2.x it is not working anymore.  

The steps I used to follow are:

1. clone the github repo on my OSX machine
2. go to the directory and input "python setup.py build"
3. "sudo python setup.py install"
4. "pyrcc4 icons.qrc -o gui/qt/icons_rc.py"
5. "sudo python setup-release.py py2app"  (which would create the Electrum.app file --> moved to the Application folder)
6. Double-click on the Electrum icon in the Application folder.

Since 2.x I get a fatal error when doing step 6...

I am on OSX 10.10.3.  Is it the new OSX Swift language that is getting in the way?

EDIT:  Traceback showing up in the console:

Code:

File "xxx/electrum/dist/Electrum.app/Contents/Resources/electrum.py", line 213, in <module>
assert os.path.exists(requests.utils.DEFAULT_CA_BUNDLE_PATH)

I would like to warn people to be very careful in providing personal information to Paybase.com.

By providing social security numbers, physical addresses, phone numbers, email addresses to those guys, you are just providing vital information to an unknown entity...  allowing them to steal your identity.

Do you know where they do business from?
Do you know their physical address?
Do you know their names and phone numbers?

If anything goes wrong, which information will you give to the law enforcement agencies?

Just my two satoshis...

 

Bots and traders have hammered the price of bitcoin in 2014. Enough is enough!

What if miners all around the world would unite and decide to strike all at once?  No more mining of bitcoin until the price goes back to decent profitability levels?

The network would stall for about 10 days - granted.  But, the message would go load and clear to those "Wall Street" traders... respect the producers of bitcoin!

Considering buying Crypsty Fee Shares on https://cryptostocks.com/securities/57.  Is it a good idea?  

The shares are currently selling at the same price as the initial offering (0.05 BTC/share) last year, and they provide you weekly dividends based on their trading fees - for life.

Looks like there is less than 8000 shares available and it seems that they gave away around 100 BTC in dividends so far.  That would be 100 BTC over 8000 x 0.05 BTC = 400 BTC, 25% interest rate.  It would be better than leaving my Bitcoins in my personal wallet for a year....

Is there anyone that purchased shares in the past that can advise me on this?

[DUE to lack of interest by the community, the CREDS project has been halted.]

DUE to lack of interest by the community, the CREDS project has been halted.