98bd66b8e
Thanks @b4rtaz! - Updated theNextPaginatedRequestResolver
class to support responses with nototal
field.
-
#912
26848dc2d
Thanks @ErnoW! - Update api types to include latest features and fixes of evmApi and streams. This includes:- removal of deprecated
subdomain
andproviderUrl
params - evm endpooint for
getMultipleNFTs
- evm endpoint updated for
getNFTContractTransfers
to includefromBlock
,toBlock
,fromDate
andtoDate
params - streams support for
getNativeBalances
- removal of deprecated
- #879
52a8160d9
Thanks @FedericoAmura! - Add support for stream triggers
-
#896
439d6e564
Thanks @b4rtaz! - Added themaxRetries
parameter to the Core config. -
#898
2dcf75f8a
Thanks @b4rtaz! - Updatedaxios
dependency to 1.2.x.
-
#846
1374573d
Thanks @ErnoW! - # Api responses (breaking change)For any api call, you get a resultAdapter response. The value of the
toJSON()
value has changed. Now it is the same value as.raw
. Previously this caused a lot of confusion, and as both return a json. The value of this method has changed. So if you used.toJSON()
on an api result you can:- Use
.result
, this will probably contain dataTypes with lots of utility functions. If you only care about the data, you can call.format()
or.toJSON()
on this datatype. This is the prefered way as it provides you wilt additional utilites and extra properties. We suggest you to use Typescript, to easily see the available properties/methods on these datatypes. - Or. use the new values (or values from
.raw
), these values are identical as they are provided by the internal api, without any data transformation. The types might be different than before, so please check this (we suggest to use Typescript, as all responses are typed, otherwise you can log the output and see any differences)
If you're using some of our internal packages @moralisweb3/core for example then these names have been changed to differentiate between server-side packages, and packages that are compatible with client-side and server-side. We name these common-*. This is a first step to provide better client-side support:
@moralisweb3/core
->@moralisweb3/common-core
@moralisweb3/evm-utils
->@moralisweb3/common-evm-utils
@moralisweb3/sol-utils
->@moralisweb3/common-sol-utils
Change your dependencies in package.json and the corresponding imports in your code to the new names.
For the time being, the old packages will remain, and we use them to forward to the common-* package, this will be removed in a future version, so please update to the new package name.
For easy integration we created a nextJs package. See
packages/next
. This contains:- hooks to all api endpoints
- adapter to integrate into NextJs authentication via Moralis Auth
For a demo check out
demos/nextjs
The parameters and return types are now exported for every api operation. These are exported from
moralis/common-evm-utils
for evm api methodsmoralis/common-sol-utils
for sol api methodsmoralis/common-auth-utils
for auth methodsmoralis/common-streams-utils
for streams methods
For example:
import Moralis from 'moralis'; import { GetContractNFTsRequest, EvmChain, GetContractNFTsResponse } from 'moralis/common-evm-utils'; const getBlockOptions: GetContractNFTsRequest = { address: '0xd8da6bf26964af9d7eed9e03e53415d37aa96045', chain: EvmChain.ETHEREUM, }; let result: GetContractNFTsResponse; const response = await Moralis.EvmApi.nft.getContractNFTs(getBlockOptions); result = response.result;
As a first step to provide better client-side support, all datatypes are now usable in server-side and client-side.
- Use
- #836
62036ef3
Thanks @sogunshola! - Change HTTP timeout to 20 seconds
- #733
77eb29bf
Thanks @ErnoW! - Sent body in delete requests. This fixes issues with Moralis.Streams.deleteAddress
- #699
d79800ad
Thanks @ErnoW! - Fix parsing of API error messages, now the MoralisError will show themessage
that is returned from the api.
- #674
c719cc2f
Thanks @sogunshola! - Added verifySignature utility function
- #658
7fffd1e4
Thanks @sogunshola! - Intergrating stream API in code base, creating a new package @moralisweb3/streams
- #597
761d0d7
Thanks @b4rtaz! - Corrected TypeScript definition of themaybe()
method. This affects on a few EVM types.
-
639053e
Thanks @ErnoW! - # Release of v2.0This release contains many breaking changes as it moves from a Javascript SDK (for react-native, browser, and NodeJs) to a NodeJs-only SDK.
Note: we will still support the v1.x version as a
moralis-v1
package (see https://github.com/MoralisWeb3/Moralis-JS-SDK-v1).These changes are to focus on Backend-only features, to facilitate self-hosted servers. Below you will find an overview of removed features and how to replace them:
- Plugins: plugins in Moralis are mostly a wrapper around an API, where the API secret is managed on the moralis backend. When using the moralis sdk in NodeJs, you can safely implement your API secret, and implement any api (opensea/pinata etc.) directly without the need of utilities in the moralis sdk
- Connecting to EVM: If you want to connect to EVM chains client-side, then this sdk is not suitable anymore. There are other open-source libraries that will have lots of utilities that can help you with this (web3js, ethers, wagmi, useDapp, web3-react)
- Server interaction: interacting with the server can be done by installing the parse-server sdk (parse).
The new sdk comes with the following featurs:
Moralis.EvmApi
: A set of methods to interact and read from EVM chainsMoralis.SolApi
: A set of methods to interact and read from Solana networksMoralis.Auth
: Utilities to implement web3 authentication in NodeJs
To get started, simply call
Moralis.start({ apiKey: 'YOUR_API_KEY' })
Then you can access the apis via
Moralis.EvmApi.account.getNFTs(options)
Moralis.SolApi.account.getNFTs(options)
Moralis.Auth.requestMessage(options)
For more info see the docs: http://docs.moralis.io Or reach out in our forums: https://forum.moralis.io
- #512
d450294
Thanks @ErnoW! - Remove Evm and Server logic. This is SDK will focus mainly on NodeJs backend implementations.
- #523
ed75131
Thanks @sogunshola! - Adding sol-utils package to codebase.
-
#560
d413073
Thanks @ErnoW! - Improve Erc20Value logic by:- geters for Erc20 for:
token.decimals
,token.name
,token.symbol
,token.contractAddress
,token.chain
,token.logo
,token.logoHash
andtoken.thumbnail
, - adding an optional token reference for
Erc20Value
. This can be used by callingErc20Value.create(amount, { token })
- fixes and additions for output of
Erc20Value
:erc20Value.value
now returns the value in a decimal string"123.567"
erc20Value.amount
returns the Bignumber value withtout taking decimals into accounterc20Value.decimals
returns the decimalserc20Value.toNumber()
returns the value in a decimal number (or throws an error if the value is too big):123.456
erc20Value.display()
returns the value in a readable string with the token symbol if available:"123.456 LINK"
(or"123.456"
)
Moralis.EvmApi.getTokenBalances()
now returns anErc20Value
object with associated token information.
- geters for Erc20 for:
- #511
30b7f4b
Thanks @sogunshola! - Refactor evmApi package to use apiUtils
- #510
7f0fc3f
Thanks @ErnoW! - Add Moralis.Auth package to handle authentication via the Moralis Authentication Api. And add a demo project for parse-server
-
#568
51e0446
Thanks @ErnoW! - Improve Evm datatypes and apply them to the EvmApi consistently:- Removed unused datatypes (mainly related to EvmTransactions)
- Add missing datatypes
- Add more properties to the EvmNft and EvmTransaction datatype
- Add constant lookups for BigNumberm EvmAddress and EvmChain
- #454
d525351
Thanks @sogunshola! - Fix resolving Ropsten and Rinkeby to the correct chainId when a new EvmChain is created by name.
- #556
36dd9a9
Thanks @ErnoW! - Add typed-emitter as dependency instead of dev-dependency. This will fix the "Cannot find module 'typed-emitter' or its corresponding type declarations" errors.
-
#568
51e0446
Thanks @ErnoW! - Improve Evm datatypes and apply them to the EvmApi consistently:- Removed unused datatypes (mainly related to EvmTransactions)
- Add missing datatypes
- Add more properties to the EvmNft and EvmTransaction datatype
- Add constant lookups for BigNumberm EvmAddress and EvmChain
-
#560
d413073
Thanks @ErnoW! - Improve Erc20Value logic by:- geters for Erc20 for:
token.decimals
,token.name
,token.symbol
,token.contractAddress
,token.chain
,token.logo
,token.logoHash
andtoken.thumbnail
, - adding an optional token reference for
Erc20Value
. This can be used by callingErc20Value.create(amount, { token })
- fixes and additions for output of
Erc20Value
:erc20Value.value
now returns the value in a decimal string"123.567"
erc20Value.amount
returns the Bignumber value withtout taking decimals into accounterc20Value.decimals
returns the decimalserc20Value.toNumber()
returns the value in a decimal number (or throws an error if the value is too big):123.456
erc20Value.display()
returns the value in a readable string with the token symbol if available:"123.456 LINK"
(or"123.456"
)
Moralis.EvmApi.getTokenBalances()
now returns anErc20Value
object with associated token information.
- geters for Erc20 for:
- #555
3f511ed
Thanks @ErnoW! - Include all files from/lib
in npm builds. This fixes a bug where only the index.js file and .d.ts files were included in builds.
- #556
36dd9a9
Thanks @ErnoW! - Add typed-emitter as dependency instead of dev-dependency. This will fix the "Cannot find module 'typed-emitter' or its corresponding type declarations" errors.
- #512
d450294
Thanks @ErnoW! - Remove Evm and Server logic. This is SDK will focus mainly on NodeJs backend implementations.
- #523
ed75131
Thanks @sogunshola! - Adding sol-utils package to codebase.
- #511
30b7f4b
Thanks @sogunshola! - Refactor evmApi package to use apiUtils
- #510
7f0fc3f
Thanks @ErnoW! - Add Moralis.Auth package to handle authentication via the Moralis Authentication Api. And add a demo project for parse-server
- #464
d4a752e
Thanks @sogunshola! - Allow to cancel an Evm connect request
- #453
ba6fd72
Thanks @sogunshola! - Add optional chain validation for chain interactions
- #488
f466f90
Thanks @b4rtaz! - Deleted the default module instances from packages, except the umbrella package (moralis
).
- #454
d525351
Thanks @sogunshola! - Fix resolving Ropsten and Rinkeby to the correct chainId when a new EvmChain is created by name.
-
#443
6ce5c1f
Thanks @ErnoW! - Alpha Release of SDK v2The SDK has been rewritten from the ground up with the aim to have a future-proof SDK that is better scalable and comes with lots of developer-experience improvements:
- First hand Typescript support
- Modular system where Functionalities split up in smaller libraries
- More consistent data handling (like addresses and chains)
- Better Error handling and error codes that help debugging
- Logging system, for easier debugging
- More flexible by providing configuration options
This first alpha release has limited functionalities and is not feature-complete compared to v1 yet. Functionalities that are included are:
- Support to be used in package managers (as npm/yarn)
- Connect to an EVM network with Metamask or Walletconnect
- Authenticate to the server via Metamask, Walletconnect or Signup/Signin with password
- Evm utilities functions as transferNative, transferErc20, and executeFunction
- EvmApi (previously web3Api)
Not supported in this release yet
- NodeJs and react-native support
- CDN import by using a script tag
- Plugins
- Solana support
- Additional connectors besides Metamask and Walletconnect
A new concept in this release is the use of Moralis datatypes. For example, all chains will be an instance of the
EvmChain
class. Then to get the chain in decimal value (like1
for etherem mainnet), just calladdress.decimal
. Or to get the value as hex-string, calladdress.hex
.These datatypes will be used everywhere within the Moralis sdk.
- Everywhere, where data is returned, we transform them to correct dataTypes. For example, all addresses returned by the EvmApi, metamask, or Moralis.Evm.Transfer will be an
EvmAddress
- Anywhere where you can provide an datatype as input, you can provide: an instance of the dataType, or any of the accepted input values for that dataType. For example: anywhere where a
chain
param is accepted, you can provide"0x1"
,1
,"ethereum"
or an excisting instance ofEvmChain
For example:
- After calling Moralis.Evm.connect, you will get an account that is an instance of
EvmAddress
, and a chain that is an instance ofEvmChain
- When providing a contractAddress in the EvmApi, you can provide an instance of
EvmAddress
, a lowercase address, or a checksum address
These classes come with more utilities, depending on the dataType, but in general these are common methods:
DataType.create("inputvalue")
, to create a new instance of the datatype. In most cases the inputvalue can be of different types. For example for EvmChain this can be:"0x1"
,1
,"ethereum"
. All values will create the same instance of the DataType.dataType.equals(value)
, will check equality of 2 different dataTypes. For example:const chain = EvmChain.create('ethereum'); chain.equals(1); // -> true chain.equals('0x1'); // -> true chain.equals(EvmChain.create(1)); // -> true
dataType.format()
: will format the dataType to a readable format. For some dataTypes, this formatting behaviour can be set in the config (when calling Moralis.start)- For object types (like
Erc20
):dataType.toJSON()
, will format the internal value to a JSON object
Overview of the most used dataTypes are:
EvmChain
: a chain/chainIdEvmAddress
an evm addressErc20
: a Erc20EvmNft
: a Erc721 or Erc1155Erc20Value
: a Erc20 value, with utilities to read the value (taking the decimals into account)EvmNative
: a representation of native currency with utils to format to wei, gwei or etherEvmTransaction
: a non published transactionEvmTransactionResponse
: a published transactionEvmTransactionReceipt
: a confirmed transaction
You can use all functionalities of Moralis by installing the main package
moralis
.But you can also opt-in to only install individual packages. To do so:
- Make sure to install the core package, this one is always required:
npm install @moralisweb3/common-core
oryarn add @moralisweb3/common-core
- Install the specific packages that you want. For example
npm install @moralisweb3/evm
oryarn add @moralisweb3/evm
- Register the installed package to the Core module, at the top of your code, before any interaction with Moralis:
import Core from '@moralisweb3/common-core'; import Evm from '@moralisweb3/evm';
Core.registerModules([Evm]);
4. Then to start/initialise: ```javascript Core.start(yourConfig)
Notes:
- some modules require certain configurations to be set. For example, to use the server module, you should provide
serverUrl
andappId
in the config - Some functionalities have dependencies on other modules. If these are not installed, you will get an error that these modules are required. For example authenticating via metamask requires not only the Server module to be installed, but also the Evm module
When calling Moralis.start, you will have more options to configure the usage of moralis. These are the options that you can specift:
logLevel
: the detail level of console.logs that you will see. This allows for easy debugging. By defaultdefaultEvmApiChain
: the default chain that is used in EvmApi callsauthenticationMessage
: the default authentication message when signing messages to authenticateappId
: your server appIdserverUrl
: your serverUrlapiKey
: your apiKey. Used for making apiCalls directly via REST instead of using your server. Only use this in your nodeJs backends.formatEvmChainId
: then default way of formatting chains (when calling chain.format())formatEvmAddress
: the default way of formatting addresses (when calling address.format())
- Register modules via
Core.registerModules([TheModule])
- Remove module via
Moralis.Core.modules.removeModule("moduleName")
- Set configuration via
Moralis.config.set("key", value)
- Read configuration via
Moralis.Core.config.get("key")
Moralis.start
accepts more configuration options
Supported connectors by moralis are exported as its own package. To use them, you need to install them seperately (except for the metamask connector, that is included by default).
Then register the connector like:
import WalletConnectConnector from '@moralisweb3/evm-wallet-connect-connector'; Moralis.Evm.connectors.register(WalletConnectConnector);
If you wish to remove them (not recommended but there might be an exotic use-case):
Moralis.Evm.connectors.remove('wallet-connect'); // Use the name of the connector
- By default, the provided chain will be used that is supplied as param
- Otherwise, the chain will be used that is used to connect to the evm (after calling
Moralis.Evm.connect
) - Otherwise, the default chain will be used. It can be set in the config when calling Moralis.start:
Moralis.start({defaultEvmApiChain: 'polygon'})
. This value will default to 'eth'
- By default, the provided address will be used that is supplied as param
- Otherwise for some endpoints that, the address will be used that is used to connect to the evm (after calling
Moralis.Evm.connect
). These are mainly theEvmApi.account
endpoints
Since the SDK has been completely rewritten, we advise to check the Typescript types, sourcecode, or response values. As some values might have changed or renamed. A lot of types have been changed to use Moralis datatypes (as EvmChain, EvmAddress etc.)
Moralis.transfer
has been split up in different functions:Moralis.Evm.transferNative
Moralis.Evm.transferErc20
,transferErc721
andtransferErc1155
Switch metamask network has been changed. It is no longer required to connect to metamask before calling this method. It can be called as
MetamaskConnector.switchNetwork('0x3');
(or any EvmChain value)Add metamask network has been changed. It is no longer required to connect to metamask before calling this method. It can be called as
MetamaskConnector.addNetwork('0x3');
(or any EvmChain value)Moralis.enableWeb3
has been renamed toMoralis.Evm.connect
. Connecting works by specifying the walletName and additional options.To connect via metamask:
Moralis.Evm.connect("metamask", {silent: false})
install the walletconnect connector package:
@moralisweb3/evm-wallet-connect-connector
Then import it and register the connector
import WalletConnectConnector from '@moralisweb3/evm-wallet-connect-connector'; Moralis.Evm.connectors.register(WalletConnectConnector);
Then call:
Moralis.Evm.connect("walletconnect", options)
- To read the connected account has been renamed to
Moralis.Evm.account
and returns anEvmAddess
- To read the connected chain has been renamed to
Moralis.Evm.chain
and returns anEvmChain
Listening to events about connecting to a network can be done by using:
- onConnecting
- onConnected
- onDisconnected
- onConnectingError
- onAccountChanged
- onChainChanged
- onProviderUpdated
Moralis.Server.authenticate('evm', { connector: 'metamask' })}
Make sure that the Walletconnect connector is added to
Moralis.Evm
:install the walletconnect connector package:
@moralisweb3/evm-wallet-connect-connector
Then import it and register the connector
import WalletConnectConnector from '@moralisweb3/evm-wallet-connect-connector'; Moralis.Evm.connectors.register(WalletConnectConnector);
Then call
Moralis.Server.authenticate('evm', { connector: 'wallet-connect', chainId: 56 })}
Setting authentication messages can be done by providing
{authenticationMessage: "Your message"}
in Moralis.startSignup to the server can now be done via a single function
Morlais.server.signUp({username, password, email, fields})
Renamed to
Moralis.Server.signIn({username, password})
To get the current user you now can use:
- For getting the user synchronously:
Moralis.Server.currentUser()
- For getting the user asynchronously:
Moralis.Server.currentUserAsync()
- To link an EvmAddress, call
Moralis.Server.linkEvmAddress
, it accepts any EvmAddress value - To unlink an EvmAddress, call
Moralis.Server.unlinkEvmAddress
, it accepts any EvmAddress value
Server classes as
Moralis.Query
,Moralis.User
etc. have been renamed toMoralis.Server.Query
,Moralis.Server.User
etc. Any missing classes or methods can be accessed by usingMoralis.Server.instance()
. This will return the instance of the server which has theQuery
,User
etc. namespaces in it.Listening to state changes regarding authentication can be done via:
- onInitialized
- onAuthenticating
- onAuthenticated
- onAutenticatingError
- onLoggedOut
Web3Api
has been renamed toEvmApi
.Response of any EvmApi request has been changed. You now get 3 result
response.result
: the returned data from the api has been transformed into more usable datatypes and more consistent formattingresponse.toJSON()
: the result fromresponse.result
but transformed into JSON objects and primitive typesraw
: the result as it is returned from the api without any changes. This is the same object a you get with manual requests, or as was implemented in v1.