User Defined Streams

Search…
Tutorials
Monitor your Smart Contract Events and External Functions
User Defined Streams — are the streams that are generated in our Platform when user uploads an Application Binary Interface (ABI) on our Portal. After an ABI is provided you can start monitoring your Smart Contract's events and function calls momentarily.
Supported Functions
Function
Is Ready
Ethereum Contract Events
​✅​
Binance Smart Chain Contract Events
​✅​
Huobi Eco Chain Contract Events
​✅​
Polygon Contract Events
​✅​
Smart Contracts' External Function Calls
​✅​
Smart Contracts' Internal Function Calls
2021Q4
Stream Name Convention
After you upload an ABI your events and external functions will be available as a separate stream with the following name pattern:
Blockchain_ContractName_EventName_Events
Blockchain_ContractName_EventName_Functions
Given an Ethereum Smart Contract with the name "MySmartContract" and event name "MyEvent" your stream name will be as following:
ETH_MySmartContract_MyEvent_Events
Given an Ethereum Smart Contract with the name "MySmartContract" and event name "Deposit" your stream name will be as following:
ETH_MySmartContract_Deposit_Events
Event Parameters
All the parameters produced by an event can be used in your Smart Trigger and can be either a part of notification that we will send to you or can be used for your business logic within a Smart Trigger.
Given an event:
event MyEvent(address indexed _address, string _name);
you will be able to utilize your parameters as @_address and @_name.
Function Parameters
All the parameters that are passed in function call can be used in your Smart Trigger and can be either a part of notification that we will send to you or can be used for your business logic within a Smart Trigger.
Given a function:
function deposit(uint256 _assetQuantity, address _from)
you will be able to utilize your parameters as @_assetQuantity and @_from.
Examples
Events
Let's assume that you uploaded your ABI with the name MySmartContract with an event:
event MyEvent(address indexed _address, string _name);
Now this event can be easily monitored using ParsiQL:
stream _
from ETH_MySmartContract_MyEvent_Events
where @contract == ETH.address("0xccec89631d2bCeB35B884c2538BcEBc245a71D0b")
​
process
  emit { @_address, @_name, message: "MyEvent was just fired."  }
end
​
Once your Smart Contract has fired an event—you will instantly get a notification (according to Smart Trigger's configuration)
Let's have another event:
event MySecondEvent(address indexed _from, address indexed _to, string _symbol);
stream _
from ETH_MySmartContract_MySecondEvent_Events
where @contract == ETH.address("0xD06cf06D1cF132F5F0b974be13Ad3bdcc633992c")
​
process
  if @_from == ETH.address("0xD849f7442857533fAe5adD8377476415cE5e79e4") 
      && @_symbol == "PRQ" then
    emit { message: "Address X just fired MySecondEvent with token PRQ." }
  end
end
Functions
Let's assume that you uploaded your ABI with the name MySmartContract with a function
function deposit(uint256 _assetQuantity, address _from)
Now this external function can be easily monitored using ParsiQL:
stream _
from ETH_MySmartContract_Deposit_Functions
where @contract == ETH.address("0xD06cf06D1cF132F5F0b974be13Ad3bdcc633992c")
​
process
  if @_from == ETH.address("0xD849f7442857533fAe5adD8377476415cE5e79e4") then
    emit { message: "Address X just made a deposit", @_from, @_assetQuantity }
  end
end
This trigger will produce the following JSON payload:
{
    message: "Address X just made a deposit",
    _from: "0xD849f7442857533fAe5adD8377476415cE5e79e4",
    _assetQuantity: 140000000000000000
}
Ocean Protocol
External Data Providers
Last modified 7mo ago
Copy link
Outline
Supported Functions
Stream Name Convention
Event Parameters
Function Parameters
Examples