Releases: BitcreditProtocol/Bitcredit-Core
Releases · BitcreditProtocol/Bitcredit-Core
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
v0.4.13
- Document versioning scheme
- Rework WASM API to return
TSResult<T> = { Success: T } | { Error: JsErrorData }without triggering exceptions - Rework
sumandcurrencyinto a coherentSumtype that's ready for multi-currency and exchange rates (breaking DB change) - Refactor the transport layer to distinguish between protocol and the rest and to use
borshfor serialization on our side - Add strong types for
SchnorrSignature,Sha256Hash,BlockId,Filetypes,Minttypes and usePublicKeyandSecretKeyin protocol types (breaking DB change) - Use bytes without encoding for bill data (breaking DB change)
- Fix plaintext-chain rendering - the nesting of
datanow works properly and oneJSON.parsecall is enough (breaking API change) - Add
IdentityTypetoIdentityCreateBlockDataandIdentityUpdateBlockData - Remove
BackupServiceandBackupStoresince it's unused - Remove file-based
FileUpload- we use surreal/nostr-based everywhere - Refactoring & Restructuring, removing cross-crate exports (breaking for Library dependents)
- Properly separate
protocolparts fromapplicationinbcr-ebill-core(breaking for Library dependents, breaking DB change) - Remove email from anon identities and contacts
- Change document max file size to 10 MB and max files on bill to 20
- Add request deadlines to BillHistoryBlock
- Remove
identity_proofAPI and adapt and move to new email confirmation API - Add dev mode flag
disable_mandatory_email_confirmations, to make it easier for testing - Identity Confirmation via Email
- Add persistence
- Adapt
create_identityanddeanonymizeto require a confirmed email for identified users - Add endpoints to
confirm,verifyan email address and toget_email_confirmations - Adapt
IdentityProofBlock to include the email confirmation signed by the mint - Split up
update_identityandupdate_emailfor identity and create identity proof block on email update - Change flow for company creation to first call
create_company_keysto get a key pair and node id, then confirm email of creator, then create company- Add
emailto signatory and use a data structure for signatories (breaking API and DB change)
- Add
- Adapt signatory handling for companies
- API for inviting signatories
- API to accept/reject company invites
- Restructured company persistence -
companytable is now a cache, calculated from the chain (similar to bills) - Added possibility to locally hide past invites
- Add notification when being invited to a company
- Add
signer_identity_proofto bill block data and verify it
- Add Contact Handshake
Version: v0.4.13
v0.4.12
- Added
actionstoBitcreditBillResult, withbill_actions, that are calculated based on which bill actions the caller is currently allowed to do (breaking DB and API change) - Fix an edge case for request to recourse if the payer == holder - they should not have past endorsees and if the payer is a contingent holder, they should not show up in past endorsees
- Fix TS types for urls
- Fix
restore from seedwhere the Nostr client wasn't connected properly - Upgrade
bcr-commonto 0.5.0
Version: v0.4.12
v0.4.11-hotfix
- Fix
restore from seedwhere the Nostr client wasn't connected properly
Version: v0.4.11-hotfix
v0.4.11
- Fix a bug where it was possible to reject recourse, even though it was already rejected
- Fixed an issue where it could happen that identity and company contacts weren't propagated to Nostr, leading to block propagation inconsistencies
- Fail with an error, if we have to connect to Nostr, but the client is not connected
Version: v0.4.11