[Discussion] Node as a Service release

Announcement URL

The LinkPool team is excited to launch our Node as a Service platform, now available at naas.link. NaaS furthers our mission of making the Chainlink network easily accessible, beginning with a focus on developers. Using the naas.link platform, developers can launch a Chainlink node in just a few clicks, removing any infrastructure complexities.

To begin with, deployments include:

  • A Chainlink node instance
  • A highly-available Postgres database
  • Direct access to clusters of Blockchain fullnodes that have been hardened through years of production experience
  • Hands off-software updates

We’re providing NaaS as a free service for developers who are building on testnet. To keep the service free and available to as many teams as possible, each user will be limited to one node. To ensure a consistent quality of service in the days following our launch, an initial global limit will also be set, though we will bump this limit up based on demand.

The launch of LinkPool’s Node as a Service platform is the product of substantial planning, effort, and our years of experience as Chainlink node operators and Chainlink ecosystem developers. We’re proud to make it available to the world and we can’t wait to see what you’re going to build.

Please feel free to comment and let us know what you think about it below! :point_down:


This is pretty cool! I think it would be a great opportunity for the Linkpool team alongside the Chainlink Advocate developers to convince the current Chainlink Fall Hackathoners reasons why they should try this system out, especially if it’s got an initial free trial which is longer then the hackathon itself.

Unless you guys already have a session for this at the hackathon haha


We’re having issues with a TOML error in setting up a job.


  1. Successfully deployed LOCAL Chainlink node with following TOML.
    type = “directrequest”
    schemaVersion = 1
    name = “Twitter Verification v0”
    contractAddress = “0x112A582C924D432bB8b05840dE0fd9B585A8f6ac”
    maxTaskDuration = “0s”
    observationSource = “”"
    decode_log [type=“ethabidecodelog”
    abi=“OracleRequest(bytes32 indexed specId, address requester, bytes32 requestId, uint256 payment, address callbackAddr, bytes4 callbackFunctionId, uint256 cancelExpiration, uint256 dataVersion, bytes data)”

    decode_cbor [type=“cborparse” data="$(decode_log.data)"]

    fetch [type=“bridge” name=“twitter-verification” requestData="{“id”: $(jobSpec.externalJobID), “data”: {“twitterHandle”: $(decode_cbor.twitterHandle), “tweetId”: $(decode_cbor.tweetId), “verificationString”: $(decode_cbor.verificationString)} }"]

    parse [type=“jsonparse” path=“data,username” data="$(fetch)"]

    encode_data [type=“ethabiencode” abi="(bytes32 value)" data="{ “value”: $(parse) }"]

    encode_tx [type=“ethabiencode”

               abi="fulfillOracleRequest(bytes32 requestId, uint256 payment, address callbackAddress, bytes4 callbackFunctionId, uint256 expiration, bytes32 data)"
               data="{\"requestId\": $(decode_log.requestId), \"payment\": $(decode_log.payment), \"callbackAddress\": $(decode_log.callbackAddr), \"callbackFunctionId\": $(decode_log.callbackFunctionId), \"expiration\": $(decode_log.cancelExpiration), \"data\": $(encode_data)}"

    submit_tx [type=“ethtx” to=“0x112A582C924D432bB8b05840dE0fd9B585A8f6ac” data="$(encode_tx)"]

    decode_log → decode_cbor → fetch → parse → encode_data → encode_tx → submit_tx


  1. On naas.link, the same TOML gives an error

422 Unprocessable Entity

Is there a Chainlink node docker version we can check against or some other TOML parser behavior difference on naas.link?

Thanks in advance!

Sorry for the delay here, hopefully this wasn’t for a Hackathon submission!

Your first step should be to head to chain.link/discord for debugging your job spec. I don’t expect that the issue has anything to do with the node itself, since they’re carbon copies of our own nodes and we’re running TOML jobs on all of them.

That said I recognize you’re indicating there’s an issue here present in our NaaS nodes that isn’t present in your own local node, so we’ll look into it.