For example, this address 0x7be8076f4ea4a4ad08075c2508e481d6c946d12b is the OpenSea contract, but on-chain the return value of querying the name attribute returns Project Wyvern Exchange. The way our code works now, we can't over ride this because we call a contract whatever it tells us to call it. We could add a field to the names data to add an 'override' name field.
Also -- in order to better price things, it would be very good to have a flag called 'stable-coin' which would instruct the pricing mechanism to return 1.0 assuming it's stable against USD.
Probably won't happen soon. If this idea resurfaces of its own, we may implement it. Keeping track of something that won't happen shouldn't happen so it won't.
We need a better ability to name addresses.
For example, this address
0x7be8076f4ea4a4ad08075c2508e481d6c946d12b
is theOpenSea
contract, but on-chain the return value of querying thename
attribute returnsProject Wyvern Exchange
. The way our code works now, we can't over ride this because we call a contract whatever it tells us to call it. We could add a field to the names data to add an 'override' name field.Also -- in order to better price things, it would be very good to have a flag called 'stable-coin' which would instruct the pricing mechanism to return 1.0 assuming it's stable against USD.