Releases: BitcreditProtocol/Bitcredit-Core
Releases · BitcreditProtocol/Bitcredit-Core
v0.4.6
- Add basic logic for implementing (social) identity proofs
- Add persistence, basic service layer and WASM API for identity proofs
- Fix block propagation inconsistencies with company identities
- Changed default relay to
wss://bcr-relay-dev.minibill.tech - Change
endorsementsendpoint, making sure all endorsees (also anon) are displayed (breaking for API because of the return type) - Add
last_block_timetostatusofBitcreditBillResult(breaking DB and API), so bill responses can be ordered by their last change - For the balance endpoint, don't add to
contingency, if the current user is only in the guarantee chain as an anon endorsee (breaking DB change)
Version: v0.4.6
v0.4.5
- Add handling for
RemoveSignatoryfrom company, which flags the company as not active - Email Notifications
- Add email notifications API
- Add email notifications registration API
- Add email notifications sending logic
- Fix issue where the notification sender defaulted to the personal identity instead of the signer identity
- Added
app_urlproperty to config - defaults tohttps://bitcredit-dev.minibill.tech(config break) - Small fix to WASM build addressing the rustwasm organization archiving
- Added an API call
sync_bill_chain, which re-synchronizes a bill via Nostr
Version: v0.4.5
v0.4.4
- Add
num_confirmations_for_paymentconfig flag and apayment_configpart of the api config, to configure the amount of confirmations needed until an on-chain payment is consideredpaid - Rewrite payment logic to iterate transactions and calculate payment state based on the first transaction that covers the amount
- We now are also able to differentiate between a payment not being sent, being in the mem pool, being paid and unconfirmed and paid and confirmed
- Add payment state for sell, recourse and bill payments to DB (breaking DB change - reset IndexedDB)
- Restructure
BillCurrentWaitingStateto remove duplication (breaking API change - checkindex.d.ts)- Add info for if a payment is in the mempool with it's transaction id, as well as how many confirmations it has, in the bill data (breaking DB change - reset IndexedDB)
- Removed the
gloodependency, since it's going to be archived - Add chain propagation for company chains and identity chain
- Implement recovery for personal identity, company identities and bills
Version: v0.4.4
v0.4.3
- Add endpoints to fetch files as base64 for identity, contacts, companies and bills
- Add option to remove files for identity, contacts and companies - if the file upload id in the payload is missing, it's ignored, if it's explicitly set to undefined, the file is removed
- Fix blank email validation for contacts and identities
- Add different file size limits for pictures (avatar/logo - 20k) and documents (invoices, registration, passport - 1mb) as well as an upper limit for bill files (100)
- This limit is checked at creation/update time, not at the time of uploading a temporary file
- Add the address of the signer for the calls to
endorsementsandpast_endorsees - Add api call
active_notifications_for_node_idsonnotificationAPI, which returns for a set of node ids, whether they have active notifications- If the set of node ids is empty, only the node ids that have active notifications are returned
Version: v0.4.3
v0.4.2
v0.4.1
- Add file and pub key to bill to share with external party and add accessors to extract data
- Upgrade wildcat and wallet-core dependencies
Version: v0.4.1
v0.4.0
- Switch to new chain transport leveraging public Nostr threads
- Add
plaintext_hashto Identity, Company and Bill Blocks, which is a hash over the plaintext data- (breaks all chains in the DB)
- Add functionality for sharing a bill with an external party, encrypted, hashed, and signed, with the plaintext block data
- Change visibility of
bill_service::errorandbill_service::serviceto private, moving the used types tobill_service - Add cargo deny
Version: v0.4.0
v0.3.17
- Changed minted proofs token format from cashu Token v3 to BitcrB (v4)
- Use NodeId, PublicKey, SecretKey and BillId types internally instead of strings (fully breaking)
- This breaks all existing databases, since the node ids and bill ids now have the format
prefix|network|pubkey- example:bitcrt03f9f94d1fdc2090d46f3524807e3f58618c36988e69577d70d5d4d1e9e9645a4f - The
prefixisbitcr - The
networkcharacter is as follows:- m => Mainnet
- t => Testnet
- T => Testnet4
- r => Regtest
- The
pubkeyis a stringified secp256k1 public key - Existing apps need to a.) delete their IndexedDB and b.) their localhost (because the mint ID might be in there)
- This breaks all existing databases, since the node ids and bill ids now have the format
- Removed
NodeIdtrait and replaced it with a concrete method on the corresponding types (breaking API change) - Rename
BillIdTS type toBillIdResponse(breaking TS type)
Version: v0.3.17
v0.3.16
- Set the BTC network in the identity and check, if the persisted network is the same as the one configured in the application, failing if it doesn't.
- Nostr npub as primary key in Nostr contacts (breaking DB change)
- Add default mint to nostr contacts as default, so it doesn't have to be added to contacts anymore
Version: v0.3.16
v0.3.15-hotfix1
- Fix Bill Caching issue between multiple identities
Version: v0.3.15-hotfix1