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
Refan
@refan
1. type : data source 2. reason : because interacting with the assetpriceoracle smartcontract is of course related to asset price data
1 reply
0 recast
1 reaction
ChristianØ
@christian
That could potentially make sense. It's hard because I want to avoid very broad tx classification but also don't want to be so specific that the classification is a rare occurrence. Thoughts?
1 reply
0 recast
1 reaction
Refan
@refan
Actually, I wanted to propose a price oracle update, but of course, many people still don't understand the meaning of the price oracle itself, so I thought that it would be asset data, but it's true that you think it's very broad,
1 reply
0 recast
1 reaction
ChristianØ
@christian
Hmmm good point. Not many outside of more technically savvy people would understand the meaning of an "Update Oracle Price" tx. But I don't think I'm particularly looking for the most human-friendly version, even though that's certainly a part of it. It's more the primary purpose of the tx. We would normally just call it "Protocol Transaction" and then leave it up the reader to see that it's updating an oracle price. But going a layer deeper and calling it "Update Oracle Price" is indeed the most accurate depiction of what occurred, whether less technical audiences understand or not.
1 reply
0 recast
1 reaction
Refan
@refan
Ah okay, very reasonable and agree,
0 reply
0 recast
0 reaction
