Content
@
0 reply
0 recast
0 reaction
ChristianØ
@christian
Bounty - 🥇 5,000 DEGEN 🥈 3,000 DEGEN 🥉 2,000 DEGEN Today, /noves classifies this as a "Protocol Transaction", but I feel that we can go a level deeper for this type of classification. Bounty Requirements: 1. What do you think the classification should be for this type of transaction, on this contract? 2. What is your reasoning? The top three most reasonable/sensible answers will win. (Transaction: https://explorer.degen.tips/tx/0x07c331ac7f4b6a5c62580736c2b578c563a1e37fda0cd333b7d958d63e4efca2) (Noves Docs: https://docs.noves.fi/reference/infrastructure) @bountybot
0 reply
1 recast
5 reactions
Bossge
@bossge
I think this is the best answer bro for protocol transaction with go deeper. Here's my answer for your 2 questions 1. The classification for this type of transaction on the contract could potentially be categorized as a "Custom Protocol Transaction." 2. The reasoning behind this classification is that the transaction may involve unique or specific protocols that differentiate it from a standard protocol transaction. By adding the term "Custom" to the classification, it highlights the specialized nature of the transaction within the context of the contract.
1 reply
0 recast
1 reaction
ChristianØ
@christian
Hmm, I don't think so. Adding the word "Custom" doesn't really describe much more in that specific tx.
0 reply
0 recast
0 reaction
Bossge
@bossge
I will describe the custom bro for that i will share what custom well be. Just like a Custom Transaction: This could refer to a broad range of activities and might not be clear to the user. And other custom token swap, custom NFT Purchase,and lastly the custom providing liq. Thanks
1 reply
0 recast
1 reaction
ChristianØ
@christian
We already have 68 transactions that cover those "custom" actions. That wouldn't work.
0 reply
0 recast
0 reaction
