Full Service

A MobileCoin service for wallet implementations.

The Full-Service Node provides ledger syncing and validation, account management, and funds transfer and receiving. It uses a JSONRPC API, so you can connect to it from command line tools or build services around its functionality. It serves the use cases of single user (and is the backing to the MobileCoin Desktop Wallet), while also serving high performance, multi-account, multi-subaddress needs (such as backing merchant services platforms).

For installation and usage instructions, get started with Full Service here!

• You must read and accept the Terms of Use for MobileCoins and MobileCoin Wallets to use MobileCoin Software.

Note to Developers

• Please see CONTRIBUTING.md for notes on contributing bug reports and code.

Table of Contents

• License
• Usage and Documentation
• Build and Run
• Build and Run
• Docker Build and Run
• Parameters
• Offline (Cold Wallet) Transaction Flow
• Contributing
• Database Schema
• Running Tests
• Linting

License

MobileCoin Full Service is available under open-source licenses. Look for the LICENSE file for more information.

Usage and Documentation

For documentation, usage, and API specification, please see the full API documentation at: High-Performance Wallet API

Database encryption features are also described in the Database Encryption section of the full API docs.

Build and Run Mob

You can build Full Service using the mobilecoin mob tool.

Prerequisites

• git
• docker
• a secret passphrase
• bash (to run outside the mob container)

Instructions

1. Clone the full-service repository using git
2. From the full-service project root, pull the submodule.

   git submodule update --init --recursive

3. Now that the submodule is pulled, you can use the mob tool by running it from the full-service project root

   ./mob prompt

If you are operating on main or test net, these steps are unnecessary; the build script will grab the relevant sigstruct. If you don't have the consensus or ingest enclaves, you may want to build the mobilecoin network to get them.

1. Create your attestation verifier seed

   MC_SEED=($(echo "<your secret phrase>" | sha256sum))

2. Build the mobilecoin network

   cd mobilecoin
   cargo build --release

3. Run the build script using the relevant network type (substitute main with test or local if appropriate)

   ./tools/build-fs.sh main

You can run full-service from within mob prompt, or exit the container to run it.

• From within the mob container, replacing main with the appropriate network type.

  ./tools/run-fs.sh main

• From outside the mob container, there are potentially extra steps
  • If running local network, copy the ingest-enclave.css file from the mobilecoin network build to where you want the runscript to pick it up from ** IMPORTANT: make sure your local instance of the local network is running before running full-service against it **

  cp ./target/docker/release/ingest-enclave.css ~/.mobilecoin/local

  • For any network, you'll need to set an environment variable before running the run-fs.sh script, replacing main with the appropriate network type.

  export CARGO_TARGET_DIR=./target/docker
  ./tools/run-fs.sh main

Build and Run

Note: Full-Service and mobilecoin are not currently compatible with Xcode 13 or higher (the Xcode that ships with OSX Monterey and later). Make sure you are using Xcode 12 before building and running Full-service. You can download Xcode 12 from Apple's developer downloads page.

Download the latest Xcode 12 and add it to your applications folder.

If you are on OSX Monterey or higher, you will need to fake the version to get OSX to allow you to open it. Follow these steps (for Xcode 12.5.1):

# Change build version to Xcode 13.1
/usr/libexec/PlistBuddy -c 'Set :CFBundleVersion 19466' /Applications/Xcode_12.5.1.app/Contents/Info.plist

# Open Xcode (system will check build version and cache it)
open /Applications/Xcode_12.5.1.app/

# Revert Xcode's build version
/usr/libexec/PlistBuddy -c 'Set :CFBundleVersion 18212' /Applications/Xcode_12.5.1.app/Contents/Info.plist

Then set your system to use it with:

sudo xcode-select -s /Applications/Xcode_12.5.1.app/Contents/Developer

1. Install Rust from https://www.rust-lang.org/tools/install

2. Install dependencies (from this top-level full-service directory).

   On Ubuntu:

   sudo apt install build-essential cmake protobuf-compiler libprotobuf-dev llvm llvm-dev clang libclang-dev libsqlite3-dev libssl-dev lcov

   On MacOS:

   brew bundle

   After openSSL has been installed with brew on MacOS, you may need to set some environment variables to allow the rust compiler to find openSSL

   Ubuntu:

   PATH="/usr/local/opt/openssl@3/bin:$PATH"
   LDFLAGS="-L/usr/local/opt/openssl@3/lib"
   CPPFLAGS="-I/usr/local/opt/openssl@3/include"
   PKG_CONFIG_PATH="/usr/local/opt/openssl@3/lib/pkgconfig"
   

   The ulimit command fixes an issue related to shell resource usage.

   MacOS:

   echo 'ulimit -n 4096' >> ~/.bash_profile
   echo 'export PATH="/opt/homebrew/opt/openssl@3/bin:$PATH"' >> ~/.bash_profile
   source ~/.bash_profile
   export LDFLAGS="-L/opt/homebrew/opt/openssl@3/lib"
   export CPPFLAGS="-I/opt/homebrew/opt/openssl@3/include"
   export PKG_CONFIG_PATH="/opt/homebrew/opt/openssl@3/lib/pkgconfig"

   Finally, for both:

   rustup component add llvm-tools-preview

3. Pull submodule.

   git submodule update --init --recursive

4. Get the appropriate published enclave measurements, which will be saved to $(pwd)/consensus-enclave.css and $(pwd)/ingest-enclave.css

   • Note: Namespace is test for TestNet and prod for MainNet.

   NAMESPACE=test
   
   CONSENSUS_SIGSTRUCT_URI=$(curl -s https://enclave-distribution.${NAMESPACE}.mobilecoin.com/production.json | grep consensus-enclave.css | awk '{print $2}' | tr -d \" | tr -d ,)
   curl -O https://enclave-distribution.${NAMESPACE}.mobilecoin.com/${CONSENSUS_SIGSTRUCT_URI}
   
   INGEST_SIGSTRUCT_URI=$(curl -s https://enclave-distribution.${NAMESPACE}.mobilecoin.com/production.json | grep ingest-enclave.css | awk '{print $2}' | tr -d \" | tr -d ,)
   curl -O https://enclave-distribution.${NAMESPACE}.mobilecoin.com/${INGEST_SIGSTRUCT_URI}

5. Install SGX libraries (required for linux distros; not required for MacOS).

   On Ubuntu:

   wget https://download.01.org/intel-sgx/sgx-linux/2.9.1/distro/ubuntu18.04-server/sgx_linux_x64_sdk_2.9.101.2.bin
   chmod +x sgx_linux_x64_sdk_2.9.101.2.bin
   sudo ./sgx_linux_x64_sdk_2.9.101.2.bin --prefix=/opt/intel

   Put this line in your .bashrc or .zhrc:

   source /opt/intel/sgxsdk/environment

   This works on more recent Ubuntu distributions, even though it specifies 18.04.

6. Put this line in your .bashrc or .zhrc:

   Ubuntu:

   export OPENSSL_ROOT_DIR="/usr/local/opt/openssl@3"

   OSX:

   echo 'export OPENSSL_ROOT_DIR="/opt/homebrew/opt/openssl\@3"' >> ~/.bash_profile

7. Build

   SGX_MODE=HW \
   IAS_MODE=PROD \
   CONSENSUS_ENCLAVE_CSS=$(pwd)/consensus-enclave.css \
   INGEST_ENCLAVE_CSS=$(pwd)/ingest-enclave.css \
   cargo build --release -p mc-full-service

8. Set database password if using encryption.

   read -rs MC_PASSWORD
   export MC_PASSWORD=$MC_PASSWORD

9. Run

TestNet Example

```sh
mkdir -p /tmp/wallet-db/
./target/release/full-service \
    --wallet-db /tmp/wallet-db/wallet.db \
    --ledger-db /tmp/ledger-db/ \
    --peer mc://node1.test.mobilecoin.com/ \
    --peer mc://node2.test.mobilecoin.com/ \
    --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/ \
    --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/ \
    --fog-ingest-enclave-css $(pwd)/ingest-enclave.css \
    --chain-id test
```

See Parameters for full list of available options.

Docker Build and Run

1. Pull submodule.

   git submodule update --init --recursive

2. Build

   This build takes advantage of features in Docker BuildKit use DOCKER_BUILDKIT=1 when building this image.

   See the Dockerfile comments for the full list of available build arguments to customize the build.

   TestNet Version

   Use --build-arg NAMESPACE=test to configure build to use TestNet enclave measurements.

   DOCKER_BUILDKIT=1 docker build -t mobilecoin/full-service:0.0.0-testnet --progress=plain \
   --build-arg NAMESPACE=test \
   --build-arg BUILD_OPTS=--no-default-features .

   MainNet Version

   Use --build-arg NAMESPACE=prod to configure build to use MainNet enclave measurements.

   DOCKER_BUILDKIT=1 docker build -t mobilecoin/full-service:0.0.0 --progress=plain \
       --build-arg NAMESPACE=prod .

3. Run

   Volumes

   This image includes VOLUME /data and configures full-service to use that path for the wallet and ledger database locations.

   If you want to save your databases outside the default volume you can use -v path/to/volume:/data but you must chown 1000:1000 path/to/volume so the app running as uid 1000 can access it.

   mkdir -p /opt/full-service/data
   
   chown 1000:1000 /opt/full-service/data
   
   docker run -it -p 127.0.0.1:9090:9090 \
       -v /opt/full-service/data:data \
       --name full-service \
       mobilecoin/full-service \
       --peer mc://node1.test.mobilecoin.com/ \
       --peer mc://node2.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/ \
       --chain-id test

   Listen and Port

   This image configures full-service to listen on the container 0.0.0.0:9090

   Use -p 127.0.0.1:9090:9090 to expose the API to you localhost.

   Run

   Required parameters are added as command options to the container.

   TestNet Example

   docker run -it -p 127.0.0.1:9090:9090 --name full-service mobilecoin/full-service \
       --peer mc://node1.test.mobilecoin.com/ \
       --peer mc://node2.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/ \
       --chain-id test

   See Parameters for full list of available options.

Parameters

Param	Purpose	Requirements
ledger-db	Path to ledger directory	Created if does not exist
peer	URI of consensus node. Used to submit transactions and to check the network block height.	MC URI format
tx-source-url	S3 location of archived ledger. Used to sync transactions to the local ledger.	S3 URI format
chain-id	The chain id of the network we expect to interact with	String

Optional Param	Purpose	Requirements
wallet-db	Path to wallet file. If not set, will disable any endpoints that require a wallet_db	Created if does not exist
watcher-db	Path to watcher directory	Created if does not exist
listen-host	Host to listen on.	Default: 127.0.0.1
listen-port	Port to start webserver on.	Default: 9090
ledger-db-bootstrap	Path to existing ledger_db that contains the origin block, used when initializing new ledger dbs.
quorum-set	Quorum set for ledger syncing.	Default includes all peers
poll-interval	How many seconds to wait between polling for new blocks.	Default: 5
offline	Use Full Service in offline mode. This mode does not download new blocks or submit transactions.
fog-ingest-enclave-css	Path to the Fog ingest enclave sigstruct CSS file.	Needed in order to enable sending transactions to fog addresses.
allowed-origin	URL of the client for CORS headers. '*' to allow all origins	If not provided, no CORS headers will be set

Parameters as Environment Variables

All available parameters can be set as Environment Variables. Parameters names are converted to SCREAMING_SNAKE_CASE and are prefixed with MC_. See full-service --help for the full list. CLI arguments take precedence over Environment Variables.

Any options that can be specified multiple times as a list (--peer, --tx-source-url) can be specified as comma delimited values.

TestNet example

MC_PEER="mc://node1.test.mobilecoin.com/,mc://node2.test.mobilecoin.com/" \
MC_TX_SOURCE_URL="https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/,https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/" \
MC_WALLET_DB="./testnet-dbs/wallet.db" \
MC_LEDGER_DB="./testnet-dbs/ledger-db/" \
MC_CHAIN_ID="test" \
MC_FOG_INGEST_ENCLAVE_CSS="$(pwd)/ingest-enclave.css" \
    ./full_service

API Key

You can add an optional API key to full service by adding a .env file to the root of this repo. The variable you need to set is: MC_API_KEY="<api key of your choosing>". If you set this env var, you must provide the X-API-KEY header in your requests to full-service.

Exit Codes

The process exit code indicates why it exited:

Code	Meaning
1	Unknown error
2	Could not connect to database.
3	Wrong database password.
4	Connecting from a banned IP address.
101	Rust Panic.

Usage and Documentation

For documentation, usage, and API specification, see our gitbook page: https://mobilecoin.gitbook.io/full-service-api/

Offline (Cold-Wallet) Transaction Flow

Full Service supports offline transactions. This flow is recommended to keep an account key on an air-gapped machine which has never connected to the internet.

The recommended flow to get balance and submit transaction is the following:

1. ONLINE MACHINE: Sync ledger by running full service.

   ./target/release/mc-full-service \
       --wallet-db /tmp/wallet-db/wallet.db \
       --ledger-db /tmp/ledger-db/ \
       --peer mc://node1.test.mobilecoin.com/ \
       --peer mc://node2.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/ \
       --tx-source-url https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/ \
       --chain-id test

2. ONLINE MACHINE and USB: Copy the ledger and the full-service binary to USB.

   cp -r /tmp/ledger-db /media/
   cp ./target/release/mc-full-service /media/

3. OFFLINE MACHINE: Create a ramdisk to store sensitive material.

   • Linux: The following will create a 512 MB ramdisk located at /keyfs.

     sudo swapoff -a
     sudo mkdir /keyfs
     sudo mount -t tmpfs -o size=512m tmpfs /keyfs

   • MacOS: The following will create a 512 MB ramdisk located at /Volumes/KeyFS.

     diskutil erasevolume HFS+ 'KeyFS' `hdiutil attach -nomount ram://1048576`

     For the remaining instructions, we will refer to /keyfs as the ramdisk location, so if on MacOS, know that this maps to /Volumes/KeyFS.

4. OFFLINE MACHINE and USB: Copy the ledger and the full-service binary to the Offline Machine.

   cp /media/ledger-db /keyfs/ledger-db
   cp /media/mc-full-service /keyfs/mc-full-service

5. OFFLINE MACHINE: Run full service in offline mode.

   ./target/release/mc-full-service \
       --wallet-db /keyfs/wallet.db \
       --ledger-db /keyfs/ledger-db/ \
       --offline \
       --chain-id test

6. OFFLINE MACHINE: You can now create or import your account, check your balance , create assigned subaddresses, and construct transactions, as outlined in the docs above. Note that your entropy, account key, and wallet.db should always remain only on the ramdisk.

7. OFFLINE MACHINE and USB: To send a transaction, you will a Construct a TxProposal using the build_transaction endpoint. The output of this call can be written to a file, such as tx_proposal.json, and then copied to the USB.

   curl -s localhost:9090/wallet \
   -d '{
   "method": "build_transaction",
   "params": {
   "account_id": "a8c9c7acb96cf4ad9154eec9384c09f2c75a340b441924847fe5f60a41805bde",
   "recipient_public_address": "CaE5bdbQxLG2BqAYAz84mhND79iBSs13ycQqN8oZKZtHdr6KNr1DzoX93c6LQWYHEi5b7YLiJXcTRzqhDFB563Kr1uxD6iwERFbw7KLWA6",
   "value": "42000000000000"
   }
   }' \
   -X POST -H 'Content-type: application/json' | jq '.result' > /keyfs/tx_proposal.json
   
   cp /keyfs/tx_proposal.json /media/

8. ONLINE MACHINE and USB: Copy the tx_proposal to the online machine.

   cp /media/tx_proposal.json ./

9. ONLINE MACHINE: Submit transaction to consensus, using the submit_transaction endpoint.

Contributing

See CONTRIBUTING.

Database Schema

To add or edit tables:

1. Ensure that you have diesel_cli installed and that it is using the current sqlite version:

   cargo install --git="https://github.com/mobilecoinofficial/diesel" --rev="026f6379715d27c8be48396e5ca9059f4a263198" diesel_cli --no-default-features --features sqlite
   

2. cd full-service

3. Create an empty version of the base db diesel migration run --database-url $MIGRATION_TEST_DB

4. Create a migration with diesel migration generate <migration_name>

5. Edit the migrations/<migration_name>/up.sql and down.sql.

6. Run the migration with diesel migration run --database-url $MIGRATION_TEST_DB, and test the inverse operation with diesel migration redo --database-url $MIGRATION_TEST_DB

Make sure that the following is still present in schema.rs before committing changes.

table! {
    __diesel_schema_migrations(version) {
        version -> Text,
        run_on -> Timestamp,
    }
}

Note that full-service/diesel.toml provides the path to the schema.rs which will be updated in a migration.

Running Tests

The simple way:

./tools/test.sh

Under the covers, this runs:

SGX_MODE=HW \
IAS_MODE=DEV \
CONSENSUS_ENCLAVE_CSS=$(pwd)/consensus-enclave.css \
CARGO_INCREMENTAL=0 \
RUSTFLAGS='-Cinstrument-coverage' \
LLVM_PROFILE_FILE="../target/profraw/json5format-%m.profraw" \
cargo test

Note: providing the CONSENSUS_ENCLAVE_CSS allows us to bypass the enclave build.

Also note: On OSX there is sometimes weird behavior when first running the test suite where some tests will fail. Opening a new terminal tab and running them again typically resolves this.

Linting

RUST_LOG=info \
SGX_MODE=HW \
IAS_MODE=DEV \
CONSENSUS_ENCLAVE_CSS=$(pwd)/consensus-enclave.css \
cargo clippy --all --all-features