Catalog npm
PACKAGE EXPLORERView in registry

@0xobelisk/sui-client

npm

Tookit for interacting with move eps framework

blockchainmoveobelisk labssui
Versions collected168
Direct dependencies39From release 2.0.0
Last observed21 Oct, 09:22 UTC

README

Current package documentation

Dubhe Client SDK

Dubhe is a client-agnostic SDK that supports various platforms including browsers, Node.js, and the COCOS game engine. It provides a simple interface to interact with your Sui Move contracts.

Getting Started

Prerequisites

Before using the SDK, make sure you have:

  1. Created and deployed your contract using the Dubhe CLI
  2. Obtained the packageId after deployment

Data Model Setup

First, define your contract's configuration using DubheConfig:

import { DubheConfig } from '@0xobelisk/sui-common';

export const dubheConfig = {
  name: 'counter',
  description: 'counter',
  systems: ['counter'],
  schemas: {
    counter: {
      structure: {
        value: 'StorageValue<u32>'
      }
    }
  }
} as DubheConfig;

Generate the contract code using CLI:

dubhe schemagen --config-path dubhe.config.ts

Initializing the Client

There are two ways to initialize the Dubhe client:

  1. Using dynamic metadata loading:
import { loadMetadata, Dubhe, NetworkType } from '@0xobelisk/sui-client';

const network = 'devnet' as NetworkType;
const packageId = 'YOUR_PACKAGE_ID';

const metadata = await loadMetadata(network, packageId);
const dubhe = new Dubhe({
  networkType: network,
  packageId: packageId,
  metadata: metadata,
  secretKey: privkey
});
  1. Using pre-saved metadata (recommended for better performance):
import metadata from './metadata.json';

const dubhe = new Dubhe({
  networkType: network,
  packageId: packageId,
  metadata: metadata,
  secretKey: privkey
});

Executing Transactions

To call contract methods:

import { Transaction } from '@0xobelisk/sui-client';

// Create transaction
const tx = new Transaction();
const params = [
  /* your parameters */
];

// Execute transaction
const response = await dubhe.tx.counter_system.inc(tx, params);

// For wallet integration
await dubhe.tx.counter_system.inc(tx, params, undefined, true);
const response = await dubhe.signAndSendTxn(tx);

Querying Data

To query contract state:

const tx = new Transaction();
const params = [
  /* your parameters */
];
const result = await dubhe.query.counter_system.get(tx, params);

// For BCS encoded results
const decodedData = dubhe.view(result);

BCS Data Decoding

The SDK provides a view() method to decode BCS-encoded return values from contract queries.

Supported Types

  • Basic types (u8, u16, u32, u64, u128, u256)
  • Boolean
  • String
  • Vector
  • Struct
  • Option
  • Custom objects

Example with Complex Types

// Example contract return type
struct GameState {
    score: u64,
    player_name: String,
    is_active: bool,
    items: vector<Item>
}

// Query and decode
const tx = new Transaction();
const result = await dubhe.query.game_system.get_state(tx, params);
const decodedState = dubhe.view(result);

Known Limitations

⚠️ Important Note:

  1. The current implementation cannot automatically decode enum types due to limitations in Sui metadata.
  2. Some complex nested structures might require additional handling.

Entity Key Generation

Dubhe provides three methods for generating entity keys:

// From object ID
const objectKey = await dubhe.entity_key_from_object(objectId);

// From string data
const bytesKey = await dubhe.entity_key_from_bytes('hello');

// From number
const numberKey = await dubhe.entity_key_from_u256(123);

Query Owned Objects

To query objects owned by a specific address:

const owner = '0xfa99b5b0463fcfb7d0203c701a76da5eda21a96190eb1368ab36a437cc89195e';
const ownedObjects = await dubhe.getOwnedObjects(owner);

Best Practices

  1. Use pre-saved metadata for better performance in production
  2. Implement proper error handling for BCS decoding
  3. Consider the limitations of enum type handling when designing your contract return types

Support

For more information or support, please visit our GitHub repository or join our community channels.

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 168

Collected releases
VersionPublishedDirect dependenciesOpen version
2.0.0Registry latest29 Jun 202639
1.2.0-pre.12522 Jun 202639
1.2.0-pre.12419 May 202639
1.2.0-pre.12318 May 202639
1.2.0-pre.12213 May 202639
1.2.0-pre.12112 May 202639
1.2.0-pre.12012 May 202639
1.2.0-pre.11911 May 202639
1.2.0-pre.1188 Apr 202639
1.2.0-pre.1177 Apr 202639
1.2.0-pre.11529 Mar 202639
1.2.0-pre.11319 Mar 202639
1.2.0-pre.11218 Mar 202639
1.2.0-pre.1108 Mar 202639
1.2.0-pre.1098 Mar 202639
1.2.0-pre.1087 Mar 202639
1.2.0-pre.1077 Mar 202639
1.2.0-pre.1067 Mar 202639
1.2.0-pre.1056 Mar 202639
1.2.0-pre.1046 Mar 202639

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
0xobelisk/obelisk-engine

Shared repository data · GitHub

License detected in repository
Not collected

Repository

PENDING
0xobelisk/dubhe

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 21 Oct, 09:22 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:a8ba5098910c2dba86dfd12dc890ca59482d8217db88b932dee54a9776d62ac1