Developer Controlled Wallets

Developer-controlled wallets enable seamless user interactions with the Web3 ecosystem. It lets you manage wallet operations, such as asset transfers and smart contract actions, on the user's behalf. This simplifies blockchain use for end users.

Before you get started, ensure that you have:

• Have a Developer Services account

• Created your API key

• (Optional) Install the applicable Server-side SDK (required if you register Entity Secret via SDK)

  Node.jsPython

  Node.js

  // Developer Controlled Wallets
  npm install @circle-fin/developer-controlled-wallets --save
  // User Controlled Wallets
  npm install @circle-fin/user-controlled-wallets --save
  // Contracts
  npm install @circle-fin/smart-contract-platform --save
  

  CopyCopied!

The Entity Secret is a randomly generated 32-byte key that secures developer-controlled wallets. It is hex-encoded, encrypted to ciphertext, and appended to API requests when creating wallets or performing transactions. For security, the ciphertext must be re-encrypted (rotated) when the API requires it. For more information, see Entity Secret Management.

The public key plays a crucial role in generating the Entity Secret Ciphertext.

Once you have the public key, you will use RSA to encrypt your Entity Secret and generate its ciphertext. Immediately after, you will transform this encrypted data into a Base64 format. The output ciphertext will be exactly 684 characters long.

You can register your Entity Secret in two ways: using the SDK or the Circle Console. The registration links your Entity Secret with your developer account.

You can use the Configurator Page in Developer Services Console to register your Entity Secret Ciphertext.

Welcome to a foundational step in utilizing our Developer Services: initiating your first API call to construct a WalletSet. We'll guide you through the process and clarify what a WalletSet entails within our platform.

A WalletSet within our ecosystem is a sophisticated grouping of wallets, securely tied together by a singular cryptographic key. Leveraging the Hierarchical Deterministic (HD) wallet technology, WalletSets offer an enhanced way to handle wallet management that spans multiple blockchain networks. This is particularly relevant for Ethereum Virtual Machine (EVM) compatible blockchains, where it is common for wallets on different networks to share the same address, thanks to the underlying technology.

As we approach the creation of your inaugural WalletSet, it's important to comprehend a critical aspect of our APIs: idempotency keys.

Idempotency is a fundamental concept which guarantees that an operation is repeatable without changing the outcome. This concept is extremely important in API requests to make sure that if a request is accidentally sent more than once, it doesn't result in duplicate operations.

Consider situations like an unstable internet connection leading to multiple unintentional request submissions, or a user who accidentally activates a command several times. Without idempotency, such events might cause numerous unwanted operations.

To prevent this, an idempotency key is used. Each request includes a distinct key that, when recognized by the server within a certain timeframe as a repeat submission, prevents the repeated processing of that request. This mechanism is crucial to preserving the integrity of your operations, ensuring that only intended actions are carried out.

Now that we've got the concept of idempotency covered, let's look at creating your WalletSet.

Let's create our first wallet set!

For a comprehensive overview of each transaction you execute with Circle's Web3 APIs, the Developer Services Console provides detailed access to API logs. By examining these logs, you gain valuable visibility into how your application interacts with Circle APIs, which can be pivotal for various aspects including troubleshooting, performance optimization, and security oversight by highlighting any abnormal activities. For detailed records of your API interactions, please refer to the API Logs section.

Within the scope of our Quickstart guide, the API log is indispensable for gaining insights into specific API calls and the objects that are created as a result. Think of the API log as a detailed record that allows you to retrieve the unique IDs of objects that have been generated, especially when these IDs are needed for subsequent API interactions. API logs are a crucial educational resource that simplify the debugging process and help you methodically comprehend the intricacies of the API's operations. Hence, the API log is not only instrumental in improving operational workflows but also serves as a valuable asset for your development projects.

Ah, the most exhilarating phase: shaping your very first developer-controlled wallet in the vastness of web3. With your prepped API key and Entity Secret Ciphertext, we're only a few steps away from crafting a masterpiece. Let's dive right in!

In web3, a wallet isn't just a storage mechanism for digital tokens or NFTs, but the very essence of user interactions on the blockchain. Essentially, it's a blend of a unique address and accompanying metadata stored on the blockchain.

For developer-controlled wallets:

With that foundational knowledge, let's get to the hands-on part.

To create a wallet you use the following parameters:

And there you have it! By the end of this step, you'll have fully functional developer-controlled wallets, ready to shape web3 experiences.

Now that you have a wallet that contains some Testnet tokens, let's dive into initiating your first transaction. It's simpler than you might think, especially with our streamlined approach.

Before we can proceed, we need to determine the tokenId. You can do this by retrieving the token balances for your wallet.

Key Transaction Parameters:

The preceding parameters are just the essentials for initiating a transaction. The endpoint offers a richer, more detailed configuration to cater to a variety of transaction types. For a comprehensive list of the supported parameters, see the official documentation.

Once you've validated your transaction and everything checks out, you're all set. Transactions on the blockchain are immutable, meaning once they're validated, they cannot be reversed or altered. So, always double-check before sending!

After initiating a transaction through our API, you can look up the transaction hash on the Dev Controlled Wallets Transactions page for in the Developer Services Console. The transaction hash is a unique identifier for your transaction.

You can validate transactions in multiple ways:

Your journey with us doesn't stop here. There's so much more to discover und dive into:

Engage, Build, Share! Dive into our forums, share your feedback, and keep an eye out for exciting challenges and hackathons. Your unique perspective and skills are valuable, and we're eager to see the innovations you'll introduce to our growing ecosystem.

Before you embark further on your journey, we'd love to hear from you. Your feedback shapes the future of our platform and helps us provide a better experience for all developers.

What did you love about the process? Was there something you wish was different? Every insight, no matter how small, matters to us.

Thank you for your trust, dedication, and enthusiasm. Here's to the next chapter in your web3 journey and the marvelous innovations you'll bring forth.

Happy Building! 🚀

Next: Explore more Quickstarts