デプロイ済みコントラクトとの対話
JavaScriptテストとコンソールコマンドを使って、デプロイ済みのスマートコントラクトとやり取りする方法を学びます。
「デプロイ済みコントラクトとの対話」はCoddyKit上の無料Blockchain Smart Contracts with Solidityレッスンです。 これはレッスン3/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはBlockchain Smart Contracts with Solidity学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Blockchain Smart Contracts with Solidityコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Why Interact with Contracts?
After deploying your smart contract, the real fun begins: interacting with it! This means calling its functions, reading its data, and sending transactions.
Interacting is crucial for:
- Testing: Ensuring your contract behaves as expected.
- dApp Frontends: Letting users connect and use your contract.
- Automation: Building scripts that perform actions on the blockchain.
Your Interaction Toolkit
When working with Hardhat or Truffle, you have powerful tools to interact with deployed contracts:
- Hardhat Console / Truffle Console: An interactive command line environment for quick tests and debugging.
- JavaScript Tests: Automated scripts that deploy (or connect to) contracts and verify their behavior.
- Custom Scripts: Standalone JavaScript files for more complex, repeatable interactions.
We'll focus on the console and JS tests today.
Hardhat Console: The Sandbox
The Hardhat Console provides a convenient way to interact with your contracts and the blockchain directly from your terminal. It uses a Hardhat Runtime Environment (HRE) that already has ethers.js and your compiled contract artifacts loaded.
To start the console, open your terminal in your Hardhat project directory and run:
npx hardhat consoleThis will launch an interactive JavaScript environment.
Connect to Your Contract
Before you can call functions, you need to "connect" to your deployed contract. This involves getting its address and creating an ethers.js Contract object that represents it.
Here's how you might do it in a Hardhat script (or directly in the console):
const { ethers } = require("hardhat");
async function main() {
// First, get the ContractFactory for your contract
const Counter = await ethers.getContractFactory("Counter");
// Replace with the actual address where your contract is deployed
const deployedAddress = "0x5FbDB2315678afecb367f032d93F642f64180aa3";
// Attach to the deployed contract using its address
const counter = await Counter.attach(deployedAddress);
console.log("Connected to Counter at:", counter.address);
}
main()
.then(() => process.exit(0))
.catch((error) => {
console.error(error);
process.exit(1);
});Calling View Functions
Functions marked as view or pure don't change the blockchain state. They are free to call and simply return data. You can call them directly from your contract instance.
Let's read the current count from our Counter contract. Note that ethers.js returns BigNumber objects for large numbers, so we often use .toString() to display them.
const { ethers } = require("hardhat");
async function main() {
const Counter = await ethers.getContractFactory("Counter");
const deployedAddress = "0x5FbDB2315678afecb367f032d93F642f64180aa3";
const counter = await Counter.attach(deployedAddress);
// Call the getCount view function
const currentCount = await counter.getCount();
console.log("Current count is:", currentCount.toString());
}
main()
.then(() => process.exit(0))
.catch((error) => {
console.error(error);
process.exit(1);
});Sending Transactions
To change the state of your contract (e.g., update a variable, transfer tokens), you need to send a transaction. These calls cost gas and require a signer (your account).
After sending a transaction, you usually await its confirmation to ensure it's mined on the blockchain. Let's increment our counter:
const { ethers } = require("hardhat");
async function main() {
const Counter = await ethers.getContractFactory("Counter");
const deployedAddress = "0x5FbDB2315678afecb367f032d93F642f64180aa3";
const counter = await Counter.attach(deployedAddress);
console.log("Incrementing count...");
const tx = await counter.increment();
await tx.wait(); // Wait for the transaction to be mined
const newCount = await counter.getCount();
console.log("Count after increment:", newCount.toString());
}
main()
.then(() => process.exit(0))
.catch((error) => {
console.error(error);
process.exit(1);
});Automated Interaction Tests
While the console is great for quick checks, automated JavaScript tests are essential for robust development. They allow you to:
- Define expected behaviors.
- Run tests repeatedly and quickly.
- Catch regressions when you make changes.
Hardhat integrates seamlessly with testing frameworks like Mocha and Chai, using ethers.js for contract interaction.
Writing an Interaction Test
A typical Hardhat test file uses describe for test suites and it for individual tests. Inside an it block, you'll connect to your contract and then call its functions, asserting the results.
Remember to replace the deployedAddress with your contract's actual address on your test network.
const { expect } = require("chai");
const { ethers } = require("hardhat");
describe("Counter Contract Interaction", function () {
let counter;
const deployedAddress = "0x5FbDB2315678afecb367f032d93F642f64180aa3"; // Your contract address
before(async function () {
const CounterFactory = await ethers.getContractFactory("Counter");
counter = await CounterFactory.attach(deployedAddress);
});
it("should read the initial count correctly", async function () {
const initialCount = await counter.getCount();
expect(initialCount.toString()).to.equal("0");
});
it("should increment the count via transaction", async function () {
const initialCount = await counter.getCount();
await counter.increment();
const finalCount = await counter.getCount();
expect(finalCount.toString()).to.equal(initialCount.add(1).toString());
});
});Smart Interaction Tips
Keep these tips in mind for effective contract interaction:
- Always Verify Addresses: Double-check the contract address you're interacting with.
- Understand Gas: State-changing transactions consume gas. Estimate costs for mainnet deployments.
- Handle Errors: Use
try-catchblocks for transactions, as they can revert. - Use Events: Listen for contract events to get structured data about transactions.
- Test Thoroughly: Write comprehensive tests for all critical functions and edge cases.
Quick Check: Interaction Types
You've learned about two main ways to interact with smart contract functions: reading state (view/pure functions) and changing state (transaction functions).
Which of the following statements about these interactions is TRUE?
Recap: Interacting with Contracts
You've successfully learned how to interact with your deployed smart contracts!
- We explored using the Hardhat Console for immediate, interactive testing.
- You saw how to connect to a deployed contract instance.
- We differentiated between calling `view` functions (free, read-only) and sending transactions (costs gas, changes state).
- Finally, we covered the importance of automated JavaScript tests for reliable contract interaction.
Next, you're ready to explore state management and storage patterns in Solidity!
よくある質問
「デプロイ済みコントラクトとの対話」レッスンは無料ですか?
はい。「デプロイ済みコントラクトとの対話」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し(組み込みコードエディタと24時間対応のAIチューター)、Blockchain Smart Contracts with Solidityコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Blockchain Smart Contracts with Solidityコースには全4レッスンが含まれています。
「デプロイ済みコントラクトとの対話」で何を学びますか?
JavaScriptテストとコンソールコマンドを使って、デプロイ済みのスマートコントラクトとやり取りする方法を学びます。 ブラウザで直接実行するハンズオンコードでBlockchain Smart Contracts with Solidityを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Blockchain Smart Contracts with Solidityを始めるのに経験は必要ですか?
事前経験は必要ありません。CoddyKitのBlockchain Smart Contracts with Solidityは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン3/4です。
「デプロイ済みコントラクトとの対話」レッスンにはどのくらい時間がかかりますか?
ほとんどのCoddyKitレッスンは約5~10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このBlockchain Smart Contracts with Solidityレッスンでコードを書いて実行できますか?
はい。すべてのBlockchain Smart Contracts with Solidityレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。
このコースのすべてのレッスン
- HardhatまたはTruffleの設定
- コントラクトのコンパイルとデプロイ
- デプロイ済みコントラクトとの対話
- コントラクトテストの作成と実行