Repository files navigation

Lower-level API for interfacing with the NEAR Protocol via JSONRPC.

Each one of the valid JSON RPC methods are defined in themethods module.For instance, to make atx request, you start with thetx moduleand construct a request using themethods::tx::RpcTransactionStatusRequest struct.

use near_jsonrpc_client::{methods,JsonRpcClient};use near_jsonrpc_primitives::types::transactions::TransactionInfo;let mainnet_client =JsonRpcClient::connect("https://archival-rpc.mainnet.near.org");let tx_status_request = methods::tx::RpcTransactionStatusRequest{transaction_info:TransactionInfo::TransactionId{hash:"9FtHUFBQsZ2MG77K3x3MJ9wjX3UT8zE1TczCrhZEcG8U".parse()?,account_id:"miraclx.near".parse()?,},};// call a method on the server via the connected clientlet tx_status = mainnet_client.call(tx_status_request).await?;println!("{:?}", tx_status);

Check outthe examples folder for a comprehensive list of helpful demos. You can run the examples withcargo. For example:cargo run --example view_account.

Versioning and releasing of this crate is automated and managed bycustom fork ofcargo-workspaces. To publish a new version of this crate, you can do so by bumping theversion under the[workspace.metadata.workspaces] section in thepackage manifest and submit a PR.

We have CI Infrastructure put in place to automate the process of publishing all crates once a version change has merged into master.

However, before you release, make sure theCHANGELOG is up to date and that the[Unreleased] section is present but empty.

Unless you explicitly state otherwise, any contribution intentionally submittedfor inclusion in the work by you, as defined in the Apache-2.0 license, shall bedual licensed as below, without any additional terms or conditions.

Licensed under either of

• Apache License, Version 2.0(LICENSE-APACHE orhttp://www.apache.org/licenses/LICENSE-2.0)
• MIT license(LICENSE-MIT orhttp://opensource.org/licenses/MIT)

at your option.