Grindery Ping Feature RoadMap

Last updated by Joe Hu 4 months ago
The following features are the possible roadmap for https://ping.grindery.org/ . The objective of this document is to better define, estimate and prioritize and at the same time better understand how these features can best be implemented at the platform level to assure reusability. 
 
 
Trigger on any token on one blockchain 
Additional comments: This is already working and requires only some bug fixing on trigger connector side 
Key questions or challenges: <what could be implemented one way or another? What are features that are hard to support? What features should/must be implemented today on App level but could more into platform level later> 
Estimates effort range: 1 - 3h 
Implementation on platform level: Currently we are using two workflows to support this. One for ERC-20 token transfer and one for wallet deposit. With recipes we will be able to do both with the single workflow. 
Implementations on  platform  level: In the short term we need only to fix bugs  
Implementations on app level: In the long term we need to use recipes 
 
 
Trigger on any token on  any supported EVM chain 
Additional comments: <more details - if needed - on the specific feature> 
Key questions or challenges: This can be implemented now using two workflows per each chain. But better to use recipes, it will allow to use any supported EVM chain with the single workflow 
Estimates effort range: 1hr for App update. <x-yh> for platform update to support recipes 
Implementation on platform level: Recipes support 
Implementations on  platform  level: App must be updated to recipes instead of multiple workflows 
Implementations on app level: <what could or should be developed at the platform level short term> 
 
Trigger on any token on  supported WASM chains (near, Flow, Algorand) 
Additional comments: how do we support blockchains that dont have nay 3ID support yet? For example: what does it take to implement a new 3ID connector? 
Key questions or challenges: We will need to create connector for the chain first, then we will figure out how to monitor token transfer on these chains and create related CDS files for them.  
Estimates effort range: 2 ~ 5h (not including time for creating chain connector) 
Implementation on platform level: (See “Key questions or challenges”) 
Implementations on app level: Add chain to list of supported chains in the UI 
 
Allow users to add and trigger with multiple wallet addresses 
Additional comments: Requires creating more workflows 
Key questions or challenges: no challenges, already supported on platform level 
Estimates effort range: 1-2hrs for the frontend + design required 
Implementation on platform level: no changes on platform level 
Implementations on app level: adding/editing/removing additional wallets UI 
 
 
Make it work for any smart contract instead of native wallet. 
Additional comments: Make it work for Gnosis-Safe or MolochDAO treasury contracts. 
Key questions or challenges: Need to figure out how the event looks like from some sample transactions. 
Estimates effort range: 2 ~ 5h 
Implementation on platform level: Research event format and create relevant CDS files. 
Implementations on app level: Create UI to build workflow similar to the existing PING app, but from new CDS files 
Implementations on app level: Find easier way to enter contract address, like querying from The Graph 
 
 
Add additional actions/channels 
Additional comments: Add Telegram, Discord, Twitter and others. This is likely more about adding the actions on the engine level? Or is there anything we need to consider at the app level? 
Key questions or challenges: <what could be implemented one way or another? What are features that are hard to support? What features should/must be implemented today on App level but could more into platform level later> 
Estimates effort range: 3 ~ 6h for each connector 
Implementation on platform level: Build connector for each service 
Implementations on app level: Add support for the new connectors 
Implementations on app level: <what could or should be developed at the platform level short term> 
 
 
Show deposit amount and corresponding currency (“3.1 ETH have been deposited by xxx”) 
Additional comments: I assume this could be hard coded. The question is rather how this could be done universally at engine level. I guess we have the same thing in our action UI on Nexus dApp? 
Key questions or challenges: One idea is to build a “Formatter” action in similar way as the one in Zapier, which can be reused in many ways. The connector may need to query The Graph or an internal database to get the correct string.  
Estimates effort range: 2 ~ 4h 
Implementation on platform level: Implement the action 
Implementations on app level: Change composed workflow to use the action to format message 
 
 
Translate sender wallet address to name based on Grindery account names 
Additional comments:Allow users to create a universal username and when sending a notification look up the username using the wallet address in our user base/directory. 
Key questions or challenges: Similar to above, create another connector to match wallet address with account name and format messages 
Estimates effort range: 3 ~ 6h 
Implementation on platform level: Implement the action, may need to change Grindery backend to support this. 
Implementations on app level: Change composed workflow to use the action to format message 
 
 
Open chain explorer with transaction details on notification click 
Additional comments: Allow to set link for the notification. 
Key questions or challenges:  
Firebase messaging connector needs to support adding a link to the notification.  
Need a way to compose a link to chain explorer based on chain id and transaction hash. Requires Formatter action I guess. 
Estimates effort range:  
Formatter action estimated here: https://docs.google.com/document/d/1CDowFHkxTyuGU4_iS16Tic5aJ66C6xtHZ1frT0-Se8E/edit?disco=AAAAc9rc1Nk .  
Connector changes must be estimated by Jin.  
Frontend update 0.5hr. 
Implementation on platform level: Implement the action, implement connector changes 
Implementations on app level: Change composed workflow to use the action to format notification link 
 
 
Add an icon to the notification 
Additional comments: Allow to set an icon for the notification. 
Key questions or challenges: Firebase messaging connector needs to support adding an icon to the notification.  
Estimates effort range:  
Connector changes must be estimated by Jin.  
Frontend update 0.25hr. 
Implementation on platform level: Implement connector changes 
Implementations on app level: Change composed workflow to include icon 
 
 
Change notification text 
Additional comments: Change text to: 
Title: Deposit detected 
Body: You received <amount> <currency> from <address> on <chain>. Click to see details. 
Once we can query usernames on our system as well as EDNS we can show names instead of wallet addresses 
Key questions or challenges: Depends on: 
Open chain explorer with transaction details on notification click 
Show deposit amount and corresponding currency (“3.1 ETH have been deposited by xxx”) 
Translate sender wallet address to name based on Grindery account names 
Estimates effort range: 0.25-0.5hr after all dependencies are completed 
Implementation on platform level: Complete dependencies 
Implementations on app level: Update composed workflows config 
 
Refreshed On: Dec 05, 2022 09:04:19 UTC+00:00