maybe store the auth somewhere, and check if it still valid from time to time / or on sensitive actions ?
+1 for a logout button !
maybe store the auth somewhere, and check if it still valid from time to time / or on sensitive actions ?
+1 for a logout button !
This is the only good solution that I see, we canât rely on apps for this. Itâs a security hole really. The only way to close this hole on the app side is to encrypt the localstorage with a password, but that defeats the purpose of your SAFE account being your single SAFE-wide login. It would also be more annoying than re-authenticating.
Cool DEAL This is something I have been looking forward to
How about the password is auto generated by the app of first use, and stored in the account?
So each app can have its own area of localStorage per account, accessible once the user has logged in?
But you need that password to get into the account with the app in the first place, or else you need to re-authenticate the app, which is what weâre trying to avoid.
safeStorage from outside the browser but still accessible by apps ? this way one cannot cheat.
Apps can already authenticate automatically if the user chooses to allow that, but you know this so I must have misunderstood, sorry.
I think Iâm the one confused actually about the lock icon functionality on the authenticator and the auth URI.
I either forgot or missed the discussion concerning the authenticator lock icon, so Iâm wondering what exactly the distinct purposes are of the URI and the lock icon. It seems that both the URI and opening the lock icon prevent any pop up for the user. Why should we bother storing the URI if the user can simply allow re-authentication of apps using the lock? And if the user doesnât want to allow that, why do apps have the option to circumvent that preference by storing the URI?
It seems to me the solution to the problem posed by @nice is to store the URI in sessionstorage (itâs probably a bit faster to reuse a URI rather than requesting a new one all the time) and if the user doesnât want a pop up after a browser restart or when opening a new tab, the user can open the lock icon.
Wow finally at home, this is so much fun.
Too bad that this transaction didnât work, I tried to send 100 typo to
polpolrene, zoki, h4xx0r, seneca, digipl, wrnice, mirror
Would be handy for friends to split up a bill
Thanks @seneca & @bzee for just coding and creating fun
This is what it should be about ants, have fun.
Did you get any error messages?
I got
polpolrene, zoki, h4xx0r, seneca, digipl, wrnice, mirror Recipient not found.
It looks like the inbox canât understand multiple recipients yet, but then comes the next problem, if it did the 100 typoâs would probably not be equally split. I tried this silly thing, because this is a feature in most regular bank apps.
But to be honest this is really amazing, we are the most wealthiest community on Earth we can create super secured non-traceable tokens out of thin air.
I just created MultiGenesisToken with all those recipients in the genesis transaction and it seems to have worked. Not sure whatâs going wrong for you. Are you on browser 0.7? Also, you need to specify the amount for every recipient, it wonât spread the first amount over all recipients.
I was just super lazy again and tried this
But I just send some typoâs the normal way
btw would it be possible to send multiple tokens? So instead of âadd recipientâ you also have a option of âAdd tokenâ?
Sure, Iâm just not sure if itâs wise to complicate the UI with such a rare use case though.
There are now 1314 Cryptocurrencies on coinmarketcap, imagine if you had a small % of each in your wallet and 21 million other people like you also, collectively you would be the biggest hedge fund on Earth.
This is how you can get a bitcoin on the SAFE Network, but it require a little trust.
Let say that I have 1000 satoshi on a bitcoin privatekey, I could create 1000 tokens + use as the New Token Name: the privatekey like so
This is the trust part, the person issuing the token needs the bitcoin wallet to add a password, this password prevents people with the privatekey from accessing the bitcoins. The nice parts is that everybody can verify that those are real bitcoins through the priv-pub keys, you have instant tx and you canât reissue the privatekey because you get this error ¨Core error: Routing client error â Data given already exists". Also you can do micro transaction with bitcoins without the bitcoin network + miners.
You donât even need to run a bitcoin node, but these 1000 satoshiâs are now out of miner control and in control of the SAFE Network. I would love for computercode to do the password setting, that way you donât have to trust no one.
I just send you guys the privatekey, if I put 1000 satoshi on 5J43rJ8JFyu57TrtRz1iEAVhXngxf29x47ibFsadZvNpfZYuDPG (on the bitcoin blockchain)
Then the value on the SAFE Network has become reality, some might argue that these tokens are not bitcoins, but bitcoin is just a privatekey which enable you to spend value on it. This goes for every blockchain assets, they are just MD on the SAFE Network.
Update for this to really work you need to destroy the other privatekey formats, by creating a token set to 0 and maybe in a comment field link to the destroyed formats.
Cons
Pros
@seneca I just issued 0.00001000 to see if i could create 1000 satoshiâs. I can, but it shows up in the wallet as 0.1. Iâve send polpolrene 0.00000100 and I see 0.9 in my wallet now instead of 0.00000900.
Thanks again for this fun stuff
Gave 1000 ⏠tokens to all you guys. I expect to be paid back in cash
This is the coolest thing on SAFE yet.
Strange, I thought I had fixed that bug earlier today. Iâll look at it again tomorrow.
Very cool, it is so good, intuitive, easy, just great! well done guys!!
I sent out a few of the very first safecoinâs to ever exist on the SafeNetwork
Wallet id: savage