Giter Club home page Giter Club logo

docs's Introduction

Website

This website is built using Docusaurus 2, a modern static website generator.

Installation

$ npm install

Local Development

$ npm start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

$ npm build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

Using SSH:

$ USE_SSH=true npm run deploy

Not using SSH:

$ GIT_USER=<Your GitHub username> npm run deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.

docs's People

Contributors

aboudjem avatar adikhanduri avatar amanraj1608 avatar andyjsbell avatar ankitshubham97 avatar arcticfloyd1984 avatar arpan-jain avatar b-venkatesh7210 avatar dabit3 avatar emmaodia avatar gabidev45 avatar gantunesr avatar gunnmgirl avatar himanshugarg06 avatar joepegler avatar khushalithakkar1993 avatar livingrockrises avatar malcodeman avatar manjeet-thadani04 avatar matthew1809 avatar megabyte0x avatar nunofilipesantos avatar omahs avatar rahat-ch avatar reetbatra avatar sruthi-manthena avatar tomarsachin2271 avatar vanshika-srivastava avatar veljkovranic avatar vgabriel45 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs's Issues

Modes of Paymaster seems unclear

How could we improve the Biconomy documentation site?

I think we should have 2 different sections along with "Integration" in Paymaster. The sections should be "Sponsored" and "ERC20", and in each one of them integration of modes should be explained respectively. In the current scenario, we have spoken about feeQuotes and response at the beginning of "Methods" section and have defined modes below it, which is quite confusing and unclear.

Revamp the overview page

  • Provide clear explanations of the product offerings
  • Improve navigation from the overview page
  • Remove all the images. paymaster images are already part of the paymaster documentation.
  • Add a demo, showcasing the UX improvements using privy.
  • add npm i sdk-package to showcase, add redirection to the quickstart page

paymaster APIs docs update

How could we improve the Biconomy documentation site?

Update decoding callData for paymaster

When trying to execute userOP via SessionSigner, validation is being done in two steps.
First step is validating when trying to do estimation for userOp and this is being done by passing the first calldata from above where we need to skip 4 bytes to get the destination contract.
Second step is validating the userOP for execution, and this is being done by passing the second calldata with paymaster where we need to skip 0x4a bytes to get the destination contract.
Add above in the docs https://docs.biconomy.io/Modules/abiSessionValidationModule#rules

[Feedback] Add simulation type usage in sendTransaction method

How could we improve the Biconomy documentation site?

The simulationType flag can be of 2 ways:
"validation" which will only simulate the validation phase, checks if user op is valid but does not check if execution will succeed
"validation_and_execution" checks if user op is valid and if user op execution will succeed
By default this flag is set to "validation"

Bundler integration and methods tsdocs update

https://bcnmy.github.io/biconomy-client-sdk/classes/Bundler.html#create - config interface and definition of optional params
https://bcnmy.github.io/biconomy-client-sdk/classes/Bundler.html#estimateUserOpGas - useropstruct and StateOverrideSet
https://bcnmy.github.io/biconomy-client-sdk/classes/Bundler.html#sendUserOp - SimulationType and UserOperationStruct
https://bcnmy.github.io/biconomy-client-sdk/classes/Bundler.html#getUserOpByHash - UserOpByHashResponse
Also add any specific details related to any methods,

[Feedback] Page: /tutorials/sendGasless

How could we improve the Biconomy documentation site?

Lacks an example demonstrating a key use case. It fails to illustrate how one interacts with a smart contract, such as invoking a gasless write operation.

Better highlight the requirement for setting rpcUrl when non ethers/ viemWallet signers are used

There are certain circumstances where the rpcUrl will be picked up when custom signers are used, but for the most part it's safe to say they will not be ingested during createSmartAccountClient unless the signer is one of those two signer types (viemWallet or ethers.Signer).

Because of this we should make it better known that rpcUrl is an available property in the config, particularly in the sections for the custom signers:
image

If rpcUrl is not provided then a default public rpc will be used - which will likely be heavily throttled and can often silently fail - so the ramifications can be nasty for end users if the dev isn't paying attention.

Add Algolia search, OpenAPI plugin and minor improvements

[Feedback] Page: /supportedNetworks

How could we improve the Biconomy documentation site?

Polygon Mumbai is outdated and missing supported ERC20 for Ethereum Sepolia thanks!

Better highlight the 'success' flag in responses

We're getting lots of reports from v4 users who are receiving a tx hash and assuming that their code is working, but they are also receiving "success" === "false" from the userOp hash without realising.

In our docs we need to better inform devs to check that success == 'true' in the responseafter they've sent a transaction. For example here, and the rest of the tutorials

See the test here as an example of how the check can be performed

We will add this check in our tests too more thoroughly so that readers of the tests notice how to measure the success of a tx.

TLDR:

Change

    const { receipt: { transactionHash }  } = await wait();

for

    const { success } = await response.wait();

throughout the docs where appropriate

Comments for the Overview on the docs

  1. The Biconomy SDK is an Account Abstraction toolkit that enables the simplest UX on your dApp and wallet << Lets include appchain here too.

  2. The Biconomy Smart Accounts are signer agnostic, which allows you to use any authorization package of your choice as long as you can pass a signer to our SDK upon the creation of a Smart Account. Check out different ways you can create a Biconomy Smart Account here. << lets be specific here that signers can be MPC or something else so its clear from the get go.

  3. Get Aditya to change the image to remove batched txn module

  4. Lets include how smart accounts are the most gas efficient in the market

  5. I would also include somewhere our stack is modular meaning that you can use the full stack or use individual components and overall prevents lock in

  6. Lets include a image for the bundler?

[Feedback] Page: /quickstart

How could we improve the Biconomy documentation site?

Hi! The full code should be this:
const userOpResponse = await smartAccount.sendTransaction({
to: nftAddress,
data: nftData,
});

const { waitForTxHash } = await smartAccount.sendTransaction({
    to: nftAddress,
    data: nftData,
});

const { transactionHash } = await waitForTxHash();
console.log("transactionHash", transactionHash);

const userOpReceipt = await userOpResponse.wait();
if (userOpReceipt.success == "true") {
    console.log("UserOp receipt", userOpReceipt);
    console.log("Transaction receipt", userOpReceipt.receipt);
}

Add error messages explanation to docs.

Would be great to have error messages explained on the docs

  1. {"code": 502, "data": undefined, "message": "An invalid response was received from the upstream server"}

Better explain simulation types and when to use them

How could we improve the Biconomy documentation site?

SimulationType === "validation" = no latency, no useful feedback: (production mode). SimulationType === "validation_and_execution" = increased latency, provides useful errors (developer mode).

Multiple users are still highlighting issues that could be resolved if they'd known and availed of our validation_and_execution mode, most recently Kwenta.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.