BlockStack : How can i setup a blockstack full node (not testnet)

hmm, it seems like you’re hitting this error from this line:

if you’re bind-mounting the blockstack-server.ini file directly, try copying it into the data directory you’ve bind-mounted and removing the explicit mount of that ini file.
docker should be able to write to that file then.

so, from my previous compose example:
cp ./blockstack-server.ini ./data/blockstack-server.ini

      - ./data:/root/.blockstack-server
      # - ./blockstack-server.ini:/root/.blockstack-server/blockstack-server.ini```

Thanks @jwiley a lot for your help. It’s working for me and i am able to ping the node using RPC. I tried those steps mentioned above and it worked perfectly fine.

Although, after some time i got an error for SegWit transactions and it suggested me to add “rpcserialversion=0” to my bitcoin node. I did that to my existing node and it worked.

I have one more question, i have looked for RPC on link provided by you and it is working. But i think it does not have all the APIs like if i want to get the transactions of a particular account as of a block height , i am unable to find a API for this.

I can see a similar API on but it is not working on my node. Could you suggest how do i get the transactions out of my existing core blockstack node?

There’s no way to directly get tx data from the v1 blockchain.
Can you set something up like our explorer ( to replicate how we do it? absolutely, but it may be more trouble than it’s worth.
There are a lot of helper services that need to run properly, and I would generally not recommend it (particularly since we’re moving to v2 soon).

So, here are some methods you can use to retrieve tx data. I’ll be using, but you should replace that with your local blockstack_core instance.
The corresponding explorer page:

  1. retrieve a block from the core node:
    curl -s | jq
    "address": "1AUjfGid6qpUo1WLWorEfarmapWMLY1BJR", 
    "block_number": 598907, 
    "consensus_hash": "0b31b297596be309954aaa5e35499e20", 
    "first_registered": 598911, 
    "importer": null, 
    "importer_address": null, 
    "last_renewed": 598911, 
    "name": "", 
    "name_consensus_hash": "4d3c4305cd6234048b11dc526e7a751e", 
    "name_hash128": "3493e9878d798aa4393eaa27e4157c2e", 
    "namespace_block_number": 373601, 
    "namespace_id": "id", 
    "op": "+", 
    "op_fee": 5500, 
    "opcode": "NAME_UPDATE", 
    "preorder_block_number": 598907, 
    "preorder_hash": "9866c7b04950c314993632fd87967924f71ad232", 
    "revoked": false, 
    "sender": "76a91467f7f9424342a0f1ab222ebbc1fb0192d43fe8ab88ac", 
    "sender_pubkey": "02841d6cb6500a30c88825c1352c5fa1fe7cea66b7d5f61f49f32ab0d5fdb54a3b", 
    "token_fee": "0", 
    "txid": "36ec00d97748ce5ce05767dbb7c547aca0ec4fca1ca48765586ec4fd04d59865", 
    "value_hash": "abccfd4584f10d2891a05f19a81f5d1c0298f414", 
    "vtxindex": 293
  1. (optional) Using a returned tx id, confirm it exists:
    curl -s | jq
  "found": true,
  "type": "btc-tx",
  "hash": "36ec00d97748ce5ce05767dbb7c547aca0ec4fca1ca48765586ec4fd04d59865"
  1. Retrieve the tx data from our explorer api: curl -s | jq

Now, some blocks obviously will have multiple tx’s in them, ex: - so you’d want to loop over that output array to retrieve each txid.

We do also rate-limit excessive traffic, so please don’t simply loop through all blocks, then retrieve the corresponding tx data.

@jwiley … Thanks a lot again for prompt reply. I will try out above given options and keep you updated. Just wanted to check do we have a tentative date when we are releasing mainnet STACKS:2.0 ?

Since i understand that V2 is a major upgrade, can you suggest if I have to again do this exercise to setup the node and any other major changes… or the same node will be upgraded directly?

I can’t give an exact date unfortunately, but this upgrade will be a hard fork so you’d have to upgrade to use the new blockchain.

The chaindata from v1 will be available once v2 reaches mainnet as well.
You can still use v1 after this upgrade, but it won’t retrieve new blocks or sync with the network, so i wouldn’t recommend it outside of research/curiosity.

I do have some docker/docker-compose docs already written to get it up and running easily:
just note the commented lines here need to have the comments removed to run - (change is PR’ed but not live).

and if you want to try running a lock mocknet: