Skip to content
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.

Commit

Permalink
Update KCT menu (#63) (#64)
Browse files Browse the repository at this point in the history
* Update KCT menu

* Update README.md
  • Loading branch information
edwin082 authored Nov 22, 2022
1 parent d3c7c1f commit c7ed376
Show file tree
Hide file tree
Showing 6 changed files with 54 additions and 45 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Klaytn Online Toolkit
Klaytn online toolkit provides code examples and github page to help to utilize the Klaytn SDK(caver-js) easily.
You can test library on: https://klaytn.github.io/klaytn-online-toolkit
You can test library on: https://toolkit.klaytn.foundation/

## Web3Modal Example
On github page, you can see web3modal demo which is derived from [web3modal/example](https://github.com/WalletConnect/web3modal/tree/master/example) and modified to add Kaikas wallet and Klip wallet. You can add support for multiple providers including Kaikas provider and Klip wallet provider by using [@klaytn/web3modal](https://github.com/klaytn/klaytn-web3modal). We have created a PR in web3modal repo, which is still under review. So we temporarily provide @klaytn/web3modal package.
Expand Down
18 changes: 9 additions & 9 deletions src/routes.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -137,29 +137,29 @@ const routes: RouteType[] = [
],
},
{
name: 'KCT',
path: '/kct',
name: 'Klaytn Tokens',
items: [
{
path: '/KCTDetection',
name: 'KCT Detection',
component: DetectKCT,
},
{
path: '/KIP7Deploy',
name: 'Deploy KIP-7 Token',
name: 'Deploy Fungible Token (KIP-7)',
component: KIP7Deploy,
},
{
path: '/KIP17Deploy',
name: 'Deploy KIP-17 Token',
name: 'Deploy Non-Fungible Token (KIP-17)',
component: KIP17Deploy,
},
{
path: '/KIP37Deploy',
name: 'Deploy KIP-37 Token',
name: 'Deploy Multiple Token (KIP-37)',
component: KIP37Deploy,
},
{
path: '/KCTDetection',
name: 'Detect Klaytn Compatible Token (KCT)',
component: DetectKCT,
},
],
},
{
Expand Down
10 changes: 6 additions & 4 deletions src/views/KCT/DetectKCT.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -83,14 +83,16 @@ const DetectKCT = (): ReactElement => {
<Container>
<Card>
<CardHeader>
<h3 className="title">Klaytn Compatible Token(KCT) Detection</h3>
<h3 className="title">Detect Klaytn Compatible Token (KCT)</h3>
<Text>
<LinkA link="https://kips.klaytn.foundation/token">
Klaytn Compatible Token
Klaytn Compatible Token (KCT)
</LinkA>{' '}
is a special type of a smart contract that implements certain
technical specifications. You can check which KCT the smart contract
implements using its address.
technical specifications. Everyone who wants to issue tokens on top
of Klaytn must follow the specification. KCT currently consists of
KIP-7, KIP-17, and KIP-37. You can check which KCT the smart
contract implements using its address.
</Text>
</CardHeader>
<CardBody>
Expand Down
21 changes: 11 additions & 10 deletions src/views/KCT/KIP17Deploy.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -305,18 +305,19 @@ const KIP17Deploy = (): ReactElement => {
<Container>
<Card>
<CardHeader>
<h3 className="title">Deploy KIP-17 Non-fungible Token (NFT)</h3>
<h3 className="title">Deploy Non-fungible Token (KIP-17)</h3>
<Text>
Here you can deploy a KIP-17 smart contract to the Klaytn Cypress or
Baobab network. Please refer to{' '}
You can deploy non-fungible token (KIP-17) contracts which provide
basic functionality to transfer NFTs on the Klaytn testnet. KIP-17
is derived from ERC-721. But, there are some differences between
KIP-17 and ERC-721; More optional extensions are defined, like
minting with URI, burning, and pausing extensions. You can find more
information{' '}
<LinkA link="https://kips.klaytn.foundation/KIPs/kip-17">
KIP-17: Non-fungible Token Standard
</LinkA>{' '}
and{' '}
<LinkA link="https://docs.klaytn.foundation/dapp/sdk/caver-js/api-references/caver.kct/kip17">
caver.kct.kip17
here
</LinkA>
.
. After successful deployment, you can find a contract account in
the block explorer.
</Text>
<PrivateKeyWarning />
</CardHeader>
Expand Down Expand Up @@ -575,7 +576,7 @@ const burned = await deployedContract.burn(burnTokenId)`}
{mintSuccess && belowPage === FunctionEnum.Transfer && (
<Card>
<CardHeader>
<h3 className="title">Send the Non-fungible Token (NFT)</h3>
<h3 className="title">Transfer the Non-fungible Token (NFT)</h3>
<Text>Enter the token Id you own and want to transfer.</Text>
</CardHeader>
<CardBody>
Expand Down
26 changes: 14 additions & 12 deletions src/views/KCT/KIP37Deploy.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,8 @@ const KIP37Deploy = (): ReactElement => {
const exURI =
'https://ipfs.io/ipfs/bafybeihjjkwdrxxjnuwevlqtqmh3iegcadc32sio4wmo7bv2gbf34qs34a/3.json'

const exTokenURI = 'http://www.wenyou.com/image/SC-01%20SCISSORS.JPG'
const exTokenURI =
'https://ipfs.io/ipfs/bafybeihjjkwdrxxjnuwevlqtqmh3iegcadc32sio4wmo7bv2gbf34qs34a/2.json'

const exAddress = '0x6CEe3d8c038ab74E2854C158d7B1b55544E814C8'

Expand Down Expand Up @@ -256,18 +257,19 @@ const KIP37Deploy = (): ReactElement => {
<Container>
<Card>
<CardHeader>
<h3 className="title">Deploy KIP-37 Token</h3>
<h3 className="title">Deploy Multiple Token (KIP-37)</h3>
<Text>
Here you can deploy a KIP-37 smart contract to the Klaytn Cypress or
Baobab network. Please refer to{' '}
<LinkA link="http://kips.klaytn.foundation/KIPs/kip-37">
KIP-37: Token Standard
</LinkA>{' '}
and{' '}
<LinkA link="https://docs.klaytn.foundation/dapp/sdk/caver-js/api-references/caver.kct/kip37">
caver.kct.kip37
</LinkA>
.
You can deploy multiple token (KIP-37) contracts. A single deployed
contract following the KIP-37 token standard may include any
combination of fungible tokens, non-fungible tokens, or other
configurations. KIP-37 is derived from ERC-1155. However, there are
some differences between KIP-37 and ERC-1155; the totalSupply
function is added to obtain the number of tokens, and more optional
extensions are defined, like minting, burning, and pausing
extensions. You can find more information{' '}
<LinkA link="http://kips.klaytn.foundation/KIPs/kip-37">here</LinkA>
. After successful deployment, you can find a contract account in
the block explorer.
</Text>
<PrivateKeyWarning />
</CardHeader>
Expand Down
22 changes: 13 additions & 9 deletions src/views/KCT/KIP7Deploy.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -117,23 +117,27 @@ const KIP7Deploy = (): ReactElement => {
<Container>
<Card>
<CardHeader>
<h3 className="title">Deploy KIP-7 Token</h3>
<h3 className="title">Deploy Fungible Token (KIP-7)</h3>
<Text>
You can deploy a KIP-7 token contract to the Klaytn blockchain.{' '}
<LinkA link="https://docs.klaytn.foundation/dapp/sdk/caver-js/api-references/caver.kct/kip7#caver-klay-kip7-deploy">
caver.kct.kip7.deploy
</LinkA>{' '}
function is used to deploy a KIP-7 token contract. After successful
deployment, you can find contract account in explorer.
You can deploy fungible token (KIP-7) contracts which provide basic
functionality to transfer tokens on the Klaytn testnet. This token
standard is ERC-20 compliant. Therefore, you can use this token
standard if you want to use ERC-20 for the Klaytn. However, there
are some differences between KIP-7 and ERC-20; More optional
functions are included like mint, burn and pause extensions. You can
find more information{' '}
<LinkA link="https://kips.klaytn.foundation/KIPs/kip-7">here</LinkA>
. After successful deployment, you can find contract account in the
block explorer.
</Text>
<PrivateKeyWarning />
</CardHeader>
<CardBody>
<h3 className="title"> Upload Deployer Keystore File</h3>
<View style={{ marginBottom: 10 }}>
<Text>
Upload keystore file. This account must have enough KLAY to deploy
a token contract.
Upload the Keystore file. This account must have enough KLAY to
deploy a token contract.
</Text>
</View>
<CardSection>
Expand Down

0 comments on commit c7ed376

Please sign in to comment.