Skip to main content
Once you have access to a Flipside data share (free or premium), you’ll need to “mount” it by creating a database from the share.

​
Prerequisites

Before mounting a share: ✅ Snowflake account in AWS US-EAST-1
✅ Enterprise Edition or higher
✅ Access to the share (via Marketplace or approval)
✅ ACCOUNTADMIN or CREATE DATABASE privileges

​
Finding your share

1

Log in to Snowflake

Log in to your Snowflake account (web UI or SnowSQL)
2

Navigate to Data

Click Data in the left sidebar, then select the Private Sharing tab
3

Locate the Flipside share

Look for shares from Flipside CryptoYou should see one or more shares listed, such as:
  • Ethereum Onchain Core Data (free)
  • Ethereum Premium Onchain Data (premium)
  • Solana Onchain Core Data (free)
  • Etc.

​
Mounting the share

1

Open the share

  1. Click on the Flipside share you want to mount
  2. You’ll see share details and available schemas
2

Create database from share

  1. Click Get
  2. You’ll see a dialog to configure the database
Mounting a data share
3

Name your database

Choose a database name:Option 1: Use the default name (recommended)
  • Usually [BLOCKCHAIN]_ONCHAIN_CORE_DATA or [BLOCKCHAIN]
  • Example: SOLANA_ONCHAIN_CORE_DATA, SOLANA
Option 2: Choose a custom name
  • Use lowercase and underscores
  • Make it descriptive
  • Example: flipside_ethereum, fs_solana_full
snowflake_custom_db

Custom Database Name

Use the default name for easier reference to documentation and examples.
4

Create the database

  1. Click Get
  2. Wait for confirmation (usually instant)
  3. The database will appear in your database list

​
Verifying the mount

After mounting, verify the share is accessible: 
-- Switch to the new database
USE DATABASE SOLANA_ONCHAIN_CORE_DATA;

-- List available schemas
SHOW SCHEMAS;

-- Expected output (for core shares):
-- CORE
-- INFORMATION_SCHEMA

-- Expected output (for premium shares):
-- CORE
-- DEFI
-- NFT
-- PRICE
-- STATS
-- INFORMATION_SCHEMA

-- Query a sample table
SELECT *
FROM solana_onchain_core_data.core.fact_blocks
ORDER BY block_id DESC
LIMIT 5;
If queries run successfully, your share is mounted correctly!

​
Managing multiple shares

You can mount shares for multiple blockchains: 
-- List all databases
SHOW DATABASES;

-- You might see:
-- ETHEREUM
-- SOLANA_ONCHAIN_CORE_DATA
-- ARBITRUM
-- Etc.

-- Query across multiple chains
SELECT 'Ethereum' AS chain, COUNT(*) AS block_count
FROM ETHEREUM_ONCHAIN_CORE_DATA.core.fact_blocks
WHERE block_timestamp >= CURRENT_DATE - 1

UNION ALL

SELECT 'Solana' AS chain, COUNT(*) AS block_count
FROM SOLANA_ONCHAIN_CORE_DATA.core.fact_blocks
WHERE block_timestamp >= CURRENT_DATE - 1;

​
Granting access to other users

If you want other users in your Snowflake account to access the shared database: 
-- Grant usage on the database
GRANT USAGE ON DATABASE ETHEREUM_ONCHAIN_CORE_DATA TO ROLE analyst_role;

-- Grant usage on all schemas
GRANT USAGE ON ALL SCHEMAS IN DATABASE ETHEREUM_ONCHAIN_CORE_DATA TO ROLE analyst_role;

-- Grant select on all tables
GRANT SELECT ON ALL TABLES IN SCHEMA ETHEREUM_ONCHAIN_CORE_DATA.core TO ROLE analyst_role;
GRANT SELECT ON ALL TABLES IN SCHEMA ETHEREUM_ONCHAIN_CORE_DATA.defi TO ROLE analyst_role;
-- Repeat for other schemas as needed

​
Unmounting a share

If you need to remove a mounted share: 
-- Drop the database
DROP DATABASE IF EXISTS ETHEREUM_ONCHAIN_CORE_DATA;
This only removes the database from your account—it doesn’t affect the underlying share. You can re-mount it anytime by following the mounting steps again.

​
Common issues

Possible causes:
  • Premium share request not yet approved
  • Wrong Snowflake account (check you’re using the AWS US-EAST-1 account)
  • Share not yet granted by Flipside
Solution:
Error: Insufficient privileges to operate on databaseSolution: You need ACCOUNTADMIN or CREATE DATABASE privilege
-- As ACCOUNTADMIN, grant privileges
GRANT CREATE DATABASE ON ACCOUNT TO ROLE your_role;
Error: Object does not exist or SQL access control errorPossible causes:
  • Database not properly mounted
  • Missing USAGE grants
  • Incorrect schema/table name
Solution:
-- Verify database exists
SHOW DATABASES LIKE 'ETHEREUM%';

-- Verify schemas
USE DATABASE ETHEREUM_ONCHAIN_CORE_DATA;
SHOW SCHEMAS;

-- Grant yourself usage
GRANT USAGE ON DATABASE ETHEREUM_ONCHAIN_CORE_DATA TO ROLE your_role;
Issue: Data hasn’t updated recentlyCheck data freshness:
SELECT MAX(block_timestamp) AS latest_block
FROM ethereum_onchain_core_data.core.fact_blocks;
See Data Freshness for expected latencies.If data is significantly stale, contact [email protected]

​
Next steps

Query optimization

Write efficient queries for better performance

Use cases

Example queries and common patterns

Data freshness

Understand update schedules and latency

Schema reference

Explore table structures and schemas