Releases: BitcreditProtocol/Bitcredit-Core
Releases · BitcreditProtocol/Bitcredit-Core
v0.5.6
v0.5.5
- Request to pay can only be done after maturity date end-of-day
- Add payment data to payment blocks (RequestToPay, OfferToSell, RequestRecourse) (breaking DB & breaking bill chain change)
- These blocks now have
payment_data: BillPaymentBlockData - Remove payment data from
SellandRecourseendorsement blocks
- These blocks now have
- Add
Option<payment_data>toBillHistoryBlockfor payment request blocks (breaking DB change) - Remove
mempool_link_for_address_to_payandlink_to_payfrom data models (breaking DB and API change) - Add endpoints to get
mempool_linkandlink_to_payto general API - Fix a bug where contingent balance was calculated wrongly, for a
payeethat was not endorsee anymore - Use taproot Addresses
- Use and validate unique payment addresses per payment request (breaking Bills on a protocol level)
- Changed
get_combined_bitcoin_key_for_billtoget_combined_bitcoin_keys_for_bill, returning all bitcoin keys for payments within this bill for the caller - Update local dev defaults for relay
- Implement endpoints to withdraw funds from a payment address
check_and_estimate_btc_sweepto get an estimate of fees with economic and fast optionssweep_btc_fundsto actually sweep the funds with the given fee
Version: v0.5.5
v0.5.4
- If the bill holder is anon, the
signing_addressneeds to not be set - If the bill holder is anon and a company, the
signatoryshouldn't have anameset (breaking DB and bill block change) - Adapt actions and status implementation for
BitcreditBillResult(breaking DB change - bill cache clear is enough- Add
payment_actionsandstatetoBitcreditBillResult - Rename
PastPaymentStatustoPaymentStatus(breaking API change)
- Add
- Add bill id in minted user token
- Add option to un-set optional fields (breaking DB change, breaking identity and company block change)
- Approach: If a field is not there, we ignore it, if it's set to undefined explicitly, we remove it
- Example (Unset):
{ "zip": undefined, "name": "Minka" }=> Removeszip - Example (Ignore):
{ "name": "Minka" }=> Ignoreszip - Example (Set):
{ "zip": "1020", "name": "Minka" }=> Setszipto 1020
Version: v0.5.4
v0.5.3
- Fix minting URL and use new bcr-common
Version: v0.5.3
v0.5.2
- Add proper block validation for Company blocks
- Add basic, deterministic algorithm for chain consensus for testing/dev
- Add basic offline mode and improve nostr reliability
Version: v0.5.2
v0.5.1-1
- Fix Mint Offer display for MintingEnabled state
Version: v0.5.1-1
v0.5.1
- Use one Nostr client for multiple identities
- Handshake - share back without contacts
- Multi-Relay Support
- Fix mempool link for mainnet
- Fix string length validation to use character count for UTF-8 support
- Fix contact shares to work bi-directional simultaneously
- Fix currency validation to be case-insensitive
- Add Esplora URL fallback support with automatic retry on errors
- Serialize
Sumamounts as strings to prevent precision loss in JavaScript (breaking change for UI) - Remove
numbers_to_wordsendpoint - Upgrade to newest bcr_common with breaking changes for minting endpoints
- Add
MintingEnabledstate toMintRequestStatusWebandQuoteStatusReply(breaking DB and API change)
- Add
Version: v0.5.1
v0.5.0-2
- Wait for Minting Status to be enabled before attempting to Mint
- Don't fail on setting recovery data again
Version: v0.5.0-2
v0.5.0-1
- Fix validation for deleting the last signatory of a company
- Fix plain text identity chain bug when accepting/rejecting an invite
- Fix company logo and file upload to use company key instead of personal key
- Fix switching to personal identity when deleting oneself from company
Version: v0.5.0-1
v0.5.0
- Stabilise Identity Proof Implementation
Version: v0.5.0