LogoLogo
  • ZENLAND DOCS
  • Getting started
    • What Is Smart Contract
    • What Is Network
    • What Is Explorer
    • What is Token
    • How Zenland works
  • FUNDAMENTALS
    • Zenland Contract
      • Contractee
      • Contractor
      • Contract Name
      • Contract Details
      • Agreed Amount
      • Contract Due Date
      • Buyer Protection Time
      • Zenland Fee
      • Zenland Fee Payer
    • Contract Chat
    • Contract Address
    • Custom Agent
    • Web3 Store
    • User Reputation
    • ZENF Token
    • Zenland Wallet
  • Contract Actions
    • What is Contract Action
    • Approve
    • Deploy
    • Transfer
    • Complete
    • Release
    • Dispute
    • Invite an Agent
    • Sync
    • Escrow user errors
  • contract states
    • What is Contract State
    • Draft State
    • Deployed State
    • Active State
    • Fulfilled State
    • Executed State
    • Disputed State
  • Smart contract types
    • Default Escrow Contract
    • Pre-Approved Contract
  • Extra
    • Tokenomics
    • Roadmap
    • Changelog
    • Contributors
Powered by GitBook
On this page

Was this helpful?

  1. Contract Actions

Sync

PreviousInvite an AgentNextEscrow user errors

Last updated 2 years ago

Was this helpful?

The "Sync" button allows manual synchronization of transaction data between a blockchain network and user interface. Syncing can be used to update the current state of a contract manually in case of miscommunication due to connection loss or accidental exit, for example.

The Sync button appears at the top right of the contract page after the contract has been deployed (published) to the selected blockchain network.

Important!

Note that there is no transaction record in the network to sync before the contract is (published) to it.

The Sync feature has been added to ensure that the user's contract page (from where the contract is managed through ) and the blockchain network (where the ) display the same at all times.

The button lets manual requests for fetching the contract transaction data through the applicable explorer API. Then, if its actual state differs from the one displayed on the page, applicable updates will be reflected on the contract page.

This gives users better control over the interface. It also ensures that the transaction status (and the contract state) is clear to prevent overriding the transaction in progress.

deployed
contract actions
contract resides
contract state