MCP_DAC VS bitshares-core

I'm using a 12-bit 2-channel SPI DAC to take digital audio information from WAV files and outputting directly to a 3.5mm audio-out jack, with a couple of electrolytic caps to AC couple the output. Try the MCP4922 chip. It connects to the ESP32 with 3 SPI pins (clock, chip select, data) and needs a 5v reference voltage. It outputs 0v-5v depending on the input values of 0 to 4095. I use this library to access the MCP4922: https://github.com/RobTillaart/MCP_DAC and it works great and the resulting audio sounds great. It's not audiofile level, but I've done public performances and nobody can really tell the difference.

BitShares Mekong 6.1.0 release with new APIs, improvements to P2P network security, Elastic Search plugin, account history plugin and more: https://github.com/bitshares/bitshares-core/releases/tag/6.1.0 All BitShares mainnet nodes and command-line wallets are recommended to be upgraded, although not required. Docker image: docker pull bitshares/bitshares-core:6.1

Testnet participants please help test the new pre-release test-6.1.0 https://github.com/bitshares/bitshares-core/releases/tag/test-6.1.0 Docker image: docker pull bitshares/bitshares-core:test-6.1 (note: bitshares/bitshares-core:test-6.1.0 is also available if you want to pin to a specific patch version).

BitShares-Core 6.0.2 release is out, all nodes please update: https://github.com/bitshares/bitshares-core/releases/tag/6.0.2

BitUSD was the first ever stablecoin. It was a decentralized, collateralized token, launched in 2014 on the BitShares platform. Every BitUSD, nominally worth $1, was backed  at the time of minting by at least $2 of BTS, the native token of BitShares. The idea was that BitUSD would be over-collateralized, even when the price of BTS fell. Unfortunately, BitUSD suffered from low liquidity and was still vulnerable to extreme volatility, ultimately losing its peg and falling from use altogether. However, the idea inspired former BitShares community members to create MakerDAO and the DAI stablecoin (see below).

BitShares-Core - full node and command line tools

* [Twitter@bitsharesorg](https://twitter.com/bitsharesorg) - Content managed by bitshares.org owner.

the easiest way to update keys is via GUI. but cli_wallet is good at generating new keys, * try the "derive_owner_keys_from_brain_key" command to generate new keys with the brain key, but please be aware of compatibility issues (will fix in next release https://github.com/bitshares/bitshares-core/pull/2355) * try the "suggest_brain_key" command to generate new brain keys and public keys (remember: the keys generated with this command is not bound to the old brain key) * for more info, try "gethelp derive_owner_keys_from_brain_key" and etc.