All notable changes to the project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Excluded unused bip39 wordlist from dist bundle, reducing bundle size.
- Fixed deprecated crypto warning in node.js usage.
handlePendingSignIn
now throws an error when overwriting an existing user session. See issue #680- Updated jsontokens library to v2.
- Updated bitcoinjs-lib dependency to v5 and eliminates node-gyp errors on install
- Fixed bugs when running in a web worker
- Method
deleteFile()
is now implemented
- Fixed return type for BlockstackNetwork.getAccountTokens
- Property
manifestURI
is now included in loaded manifest object - The
src
directory is now included in the npm package
- Converted codebase to Typescript
- New
dist/blockstack.js
bundle with ES2015/ES6 support - `lib/**/*.js modules with Node v8.x support (ES2015/ES6 & CommonJS modules)
- Fixed protocol handler detection issues with modular usage of blockstack.js
- New function
getFileUrl()
will return a URL for reading a particular file from an applications' Gaia bucket.
- Fixed the email authentication scope
- Fixed multiple bugs with
redirectToSignIn()
andmakeAuthRequest()
- Moved common user session related functions into
UserSession
. Session configuration is done through AppConfig objects. This change removes the library's dependency on browser environments. - List of functions moved: redirectToSignIn(), isUserSignedIn(), isSignInPending(), handlePendingSignIn(), loadUserData(), signUserOut(), getFile(), putFile(), encryptContent(), decryptContent(), listfile(), deleteFile()
- The public API will remain backward compatible until a future release.
loadUserData()
now throws an error instead of returning null if no signed in user session is detected
- New method for auth protocol handler detection. This should fix sign in flows for most major web browsers and operating systems with both the native browser installed and not installed.
- NOTE: If you're using this version of blockstack.js with an old version of the native browser, the app will (1) open an auth handler in the native browser and (2) also redirect the original tab to browser.blockstack.org.
- Added automatic retry logic to
putFile
in the case of a failed storage call. This might be the case if there have been any token revokations. This new logic will catch the first failed write, construct (and cache) a new Gaia token, and then attempt the write again. This allows tokens to be revoked without any hiccups from a user experience standpoint.
- Added an extra parameter to
makeAuthRequest
, calledextraParams
. This is a wildcard object, and all keys and values included in this argument will be included in thepayload
of anauthRequest
. authRequest
version bumped to1.3.1
from1.3.0
.
- The
BlockstackWallet
class inblockstack.js
supports generating private keys and addresses within the hierarchical derivation scheme used by the Blockstack Browser and supported by the Blockstack ecosystem. - A
listFiles
function allows an application to list files in its Gaia storage bucket. - In the transaction generation library, the makeTX functions now take an optional 'buildIncomplete' argument, allowing you to get a serialized transaction which hasn't been fully signed yet.
- A
blockstackAPIUrl
field to the authentication response token that overrides the default inblockstack.config.network
allowing the user to specify their own Blockstack Core node. - A
gaiaAssociationToken
field to the authentication response token which enables users to run private Gaia hubs without authorization each application address. - An option
contentType
to theputFile
options
object that sets the Content-Type header for unencrypted data. Thanks to @muneebm for this!
- Fixed a bug in version checking during the authentication process that manifested itself when signing in with apps using very old versions of blockstack.js.
- Default redirect URI changed from origin plus trailing slash to the
origin. For example, app with origin
https://example.com
default redirect URI which was previouslyhttps://example.com/
is nowhttps://example.com
. - Fixed a couple bugs in the transaction generation, networking code. First, coerce address now correctly coerces P2SH addresses. Second, bitcoinjs-lib recently switched to defaulting to version 2 transactions, which breaks our interoperability with a handful of other libraries. Finally, with this comes a little bit of refactoring, to reduce the repeated code in the transaction libraries.
- Increments the authentication process version to 1.3 in a backwards compatible change.
- When using the bitcoind client in development networks,
track which addresses we've already called
importaddress
with and do not retry.
- Resolve unsupported protocol error by redirecting to hosted authenticator on all mobile devices
- Resolve unsupported protocol error by redirecting to hosted authenticator on iOS
- Update
bitcoinjs-lib
to version 4.0.0.
- Switched from
cross-fetch
tocross-fetch/polyfill
to fix a bug that caused network requests to fail in node environments
- Support for
verify
andsign
keywords ingetFile
andputFile
respectively. This enables support for ECDSA signatures on SHA256 hashes in the storage operations, and works for encrypted and unencrypted files, in addition to multi-player reads (for unencrypted files). - New
TransactionSigner
interface to allow for different signing agents in thetransactions
functions (e.g., makePreorder). putFile
can now optionally take the public key for which you want to encrypt the file. Thanks to @bodymindarts for this!handlePendingSignIn
now acceptstransitKey
as an optional 3rd parameter. This enables support for more complex sign in flows.
- The gaia hub connection functions now use a JWT for authentication,
the "v1" gaia authentication token. This is not a backwards
compatible change-- an app using this version of
blockstack.js
will refuse to downgrade to the old protocol version unless the old gaia authentication provides a very specific challenge text matching the normal gaia hub challenge text. encryptContent
now takes a public key instead of a private key to encrypt content for other users.- The validateProofs() method now handles errors in proof-checking more seamlessly, properly catching failed promises. Previous error cases which resulted in uncaught exception warnings and null responses should now behave correctly.
handlePendingSignIn
now takes a second parameter which is the signed authentication response token. Thanks to @muneebm for this!- Fixed an issue in
ecPairToHexString
that may result in generation of an incorrectly hex string encoding of the private key. - Proofs now support subdomains.
- Updated a number of dependencies to fix know vulnerablities.
- Switched from isomorphic-fetch to the better maintained cross-fetch which will improve functionality of the library in node environments.
encryptContent
anddecryptContent
methods for encrypting strings and buffers with specific keys, or by default, the appPrivateKey. Thanks to @nikkolasg and @nivas8292 for PRs on this work.- Functions in
transactions
to support namespace creation (NAMESPACE_PREORDER
,NAMESPACE_REVEAL
,NAMESPACE_IMPORT
,ANNOUNCE
, andNAMESPACE_READY
). Thanks @jcnelson. - Support for
NAME_REVOKE
transactions. Thanks @jcnelson. transactions.AmountType
Flow union type that captures both the type of JSON response from the stable/v1/prices/*
RESTful endpoints on Blockstack Core, as well as the upcoming/v2/prices/*
endpoints.- Support for setting
blockstack.js
logLevels viaconfig.logLevel
. Supports strings:['debug', 'info', 'warn', 'error', 'none']
and defaults todebug
. If you do not wantblockstack.js
to print anything toconsole.log
, use'none'
. Thanks @hstove.
- Modified the transaction builders in
transactions.js
to accept a new flow typetransactions.AmountType
for the price of a name or namespace. This makes them forwards-compatible with the next stable release of Blockstack Core. - Added inline documentation on the wire formats of all transactions.
- Update to proof URLs for instagram proofs. Thanks @cponeill.
- Fixes to several safety checks. Thanks @jcnelson.
- Fixed error handling in proof validation -- several errors which would cause uncaught promise rejections now are handled correctly.
- Improved error handling in authentication -- if a user tries to sign in with an application is a different browser context, rather than experiencing a 'Key must be less than curve order' error, the authentication fails.