barnjamin / abi-uri Goto Github PK

to mirror the ABI spec more closely, what if the URI was formatted like:

algorand-abi://APP_ID/METHOD_SELECTOR?args=arg_1,arg_2&note=some%20not%20so%20secret%20msg&apat=acct_xyz

args could also accept multiple vals for arrays:
?args=arg_1&args=arg_2&args=(arg_3_op1,arg_3_op2) where args = [ arg_1, arg_2 ] AND the user/signer picks which option for arg_3 in the signing app.

• since the order of method args is particular + the method selector specifies their types, the args param should be an ordered array and types parsed accordingly (note, there are a few standards re how to injest arrays in query strings)
• all algo txn fields: https://developer.algorand.org/docs/get-details/transactions/transactions/#common-fields-header-and-type
• the type param could be locked to appl since this all about abi application calls, though perhaps this can be the same spec as algorand://... and handle all types of algo txns
• should the args param be called apaa as per the docs? or accept both?
• a range / selectable options can be handled like =(option_1,option_2,option_3)
• objects can be consumed stringified like ={key_1:val_1,key_2:(val_2a,val_2b)}
• METHOD_SELECTOR looks something like: reverse(string)string so args must be length of 1 + type: string
• METHOD_SELECTOR == apaa[0]
• APP_ID == apid (inferred from base)
• for testnet app calls specify a testnet APP_ID and gen=testnet-v1.0&gh=SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=
• other important fields: apas apfa apan

predefining a txn for a client to sign + send will be HUGE ! 👏 @barnjamin