dont need to check for sighash then, which is good news :D
> AIP does use bitcoin signed messages ...
you are welcome to write whatever libs that help you manage accesing lower level apis tho
relayone is not intended to provide high level api, you can consider everything deprecated outside of relayone.send('rawtx'), relayone.encrypt/decrypt/sign
no what i mean is AIP happened before paymail, i think there is no way to lookup paymail from the signing key in paymail spec either
ideally AIP uses bitcoin signed message :D
is there anythin about identity in bitcoin social schema tho 🤔
like if there is no good way for relay to understand that this is askbitcoin transaction we will pop permission prompt on each sign op
have you considered using map, its bad but it is what everyone uses
well aip is pretty clear, pipe and i will sign whatever is before me, so i would like to keep it like it is :D
no third party lib, scripts in relay look like (OPCODE|BUFFER)[] where opcode is number for opcode and buffer is pushdata
we need a code that checks that whatever is left of AIP bitcom is not sighash, ideally we want to parse everything that is before that as well
relayone.sign('blah | blah | blah | AIPBITCOM')
> We can probably start by specifying how the API should work for relayone and API. Some examples of how you would like to use it in AskBitcoin or another project would be rather handy.
whoever wants to add aip to relayone - raise yer hand
Make it pick up twetch.app session
All conversations may be intense. its in tos
