Source: https://daphnislabs.com/services/eos-development

# EOS Blockchain Development

New applications and support for EOS-origin blockchain systems, with chain-specific contracts, account permissions and wallet integration agreed before implementation.

[Discuss your project](https://daphnislabs.com/contact?service=eos-development) [Try the example](https://daphnislabs.com/services/eos-development#worked-example)

**Owner**

**Active permission**

**Contract action**

transfer(A-104) **Chain receipt**

Authorization is checked before the action changes state.

## Tools & technologies

-   Chain-specific contract SDK
-   RPC APIs
-   Wallet adapter
-   Transaction indexer

## Record an approved asset transfer

Capability Example

An authorized account requests a transfer of a registered digital asset.

### Check

### Sign

### Confirm

Illustrative data. Nothing is sent to an external system.

Example workspace 1 / 3

### Transfer request

```
Asset: A-104
Actor: account.alpha
Required permission: active
```

Validate ownership and the permission required by the contract.

### Signed transaction

```
User reviews recipient
Wallet signs authorized action
Transaction submitted to selected network
```

Present the exact transaction to the account's wallet.

### Chain receipt

```
Transaction reference recorded
Ownership read from confirmed state
Failure leaves a recoverable request
```

Update the application only after the required chain confirmation.

A transaction reference and updated asset ownership, or a recoverable failure state.

Follow the record through the next step

## Applications on an explicitly chosen chain.

### Contract applications

Implement explicit state transitions and authorization for an agreed chain runtime.

### Wallet integration

Prepare transactions for signing and display their confirmed status.

### Existing EOS systems

Review contracts, dependencies and compatibility with the target network's current tooling.

## Contracts, clients and chain-specific checks.

-   **Contract source and test suite**
-   **Permission and resource plan**

-   **Wallet/API integration**
-   **Deployment and recovery runbook**

## Verify the network and its current tooling.

### Network identity

Confirm the specific EOS-origin or Vaulta environment, runtime and wallet support; names alone do not establish compatibility.

### Contract review

Independent security assessment and key custody are separate responsibilities to define before release.

## Questions before we start.

### Can you build a new application as well as maintain an existing one?

Yes. New work starts with a compatibility check of the intended chain, SDK and account model; support starts with the deployed contract and its permissions.

### Can contract changes be rolled back?

Only within the controls the chain and application permit. Upgrade authority, migrations and irreversible transactions need a documented release plan.

[Blockchain Development](https://daphnislabs.com/services/blockchain) [Smart Contract Development](https://daphnislabs.com/services/smart-contract-development) [Ethereum Development](https://daphnislabs.com/services/ethereum-development)

## Bring your starting point.

Share the chain, contract addresses, permission model and the transaction workflow you want to build.

[Discuss your project](https://daphnislabs.com/contact?service=eos-development) [Explore related services](https://daphnislabs.com/services/blockchain)