🔐
Trust Enterprises
  • Getting Started
  • Intro video course
    • Introduction of the Trust Enterprises project [2:16]
    • Deployment of your first Serverless client [6:29]
    • Using Postman with the Trust Enterprises API [6:33]
    • Installation of the Trust Enterprises Laravel package [7:51]
    • Basic interaction with your client with Laravel. [10:28]
  • Deployment
    • Vercel
    • Environment Variables
    • Github Actions
  • REST API
    • Overview
    • Inscriptions
      • Deploy an Inscription
      • Mint an Inscription
      • Burn an Inscription
      • Transfer an Inscription
    • NFT Ecosystem
      • Create an NFT Collection
      • Generate Metadata
      • Mint an NFT
      • Transfer an NFT
      • Claiming NFTs through Passes
    • Accounts
    • Tokens
      • Create a token
      • Bequesting a token
      • Token Holdings and Balance
    • Topics
      • Get topic info
      • Creating a new topic
      • Updating a topic
    • Consensus Messages
    • Balance
    • Status
    • Webhooks
  • The Laravel Client
    • Overview
    • Installation
    • Interacting with your client
    • Create a Marketplace
    • Manage your Inscription Flow
    • Checking account balances and sending tokens
  • Contributing
    • Local Development
      • Architecture Rationale
    • Contributing Guidelines
    • Changelog
  • Links
    • Github
    • Trust Enterprises
    • Postman Documentation
    • Hedera Network Status
    • Remote Software Development
Powered by GitBook
On this page
  • Deploying an Inscription
  • Imports
  • Code
  • Mint an Inscription
  • Code
  • Burn an Inscription
  • Code
  • Transfer an Inscription
  • Code

Was this helpful?

  1. The Laravel Client

Manage your Inscription Flow

The Laravel client provides the programmatic ability to manage the entire lifecycle of inscriptions, for deployments, minting, burning, and transferring.

This provides inscription capibility for PHP, you can view the tests where appropriate but the features mirror the inscription API for:

  • deploying

  • minting

  • burning

  • transferring

Every response through the Inscription methods will return a InscriptionResponse object that includes the raw inscription data and related consensus message ids for storage.

This feature is considered to be in an Alpha state, and that any code may change at anytime. We may additionally update this documentation to reflect the updated standards for dealing with this meta-protocol.

Have fun!

These examples consider a private topic as a points system on testnet. If you don't set the private topic on mainnet it will default to the default HCS-20 topic

Deploying an Inscription

Imports

use Trustenterprises\LaravelHashgraph\LaravelHashgraph;
use Trustenterprises\LaravelHashgraph\Models\Inscriptions\BurnInscription;
use Trustenterprises\LaravelHashgraph\Models\Inscriptions\DeployInscription;
use Trustenterprises\LaravelHashgraph\Models\Inscriptions\MintInscription;
use Trustenterprises\LaravelHashgraph\Models\Inscriptions\TransferInscription;

Code

$deploy = new DeployInscription('TICK1', 'Ticker', 300);
$deploy->setPrivateTopic("7459744");

$minted = LaravelHashgraph::deployInscription($deploy);

Mint an Inscription

Code

$mint = new MintInscription('TICK1', '0.0.1', 1);
$mint->setPrivateTopic("7459744");

$minted = LaravelHashgraph::mintInscription($mint);

Burn an Inscription

Code

$burn = new BurnInscription('TICK1', '0.0.1', 1);
$burn->setPrivateTopic("7459744");

$minted = LaravelHashgraph::burnInscription($burn);

Transfer an Inscription

Code

$transfer = new TransferInscription('TICK1', '0.0.1', '0.0.2', 1);
$transfer->setPrivateTopic("7459744");

$minted = LaravelHashgraph::transferInscription($transfer);
PreviousCreate a MarketplaceNextChecking account balances and sending tokens

Last updated 1 year ago

Was this helpful?