Project Decorum - Wallet Release

Apps
21

Are you sure you are on SAFE Browser 0.7? Also, try unlocking the small lock icon in the Authenticator.

2 Likes
22

Ah! Not the newest version. Thanks. Iā€™ll check the lock too.

3 Likes
23

I (as the central bank for Troons :sunglasses:) got some errors with both names. I tried the lower and uppercase versions. So let me know when the wallets are connected to the public names and Iā€™ll try again.

2 Likes
24

Yeah, Iā€™m having some bugs and donā€™t have time to sort it now. Not sure if the errors are all mine or a mix. I know at least one was using an old browser.

Iā€™ll send you a request when I have a chance to debug.

All very cool, though.

3 Likes
25

Okā€¦ I can finally pack in the day job.
Can someone tell me how to get my coins to an exchange? :joy::joy::joy::joy::joy:

image

Who wants some BCH?

12 Likes
26

Great job! @anon40790172 I urgently need some Troons! :smiley: Public name: h4xx0r

2 Likes
27

Check your wallet. plus 20 char

3 Likes
28

Public-IDs that have a wallet:

  • polpolrene
  • zoki
  • h4xx0r
  • seneca
  • digipl
  • wrnice
  • mirror
2 Likes
29

My god. The transaction speed is instant. LOLOLOLOLOLOLOLOLOL
SAFENetwork will replace etherium.

7 Likes
30

This is amazing. ProjectDecorum is a gamechanger, it also shows of the capabilities of the safenetwork very well.

via Imgflip Meme Generator

12 Likes
31

Haha omg, so many coins. :smiley: Reminds me of the old days where you would just casually send hundreds of bitcoins. Will hodl these Troons for ever!

EDIT: At least until next Alpha. ^^

5 Likes
32

Hey if Litecoin can reach a $4bn cap why not Troons? :laughing:

4 Likes
33

I created a wallet for : wrnice :slight_smile: really cool stuff here !!

Spotted an issue though :
If I sign into the authenticator under , say, myUser1 , and visit the wallet, I can create, use ,etcā€¦ wallets under myUser1ā€™s public IDS.

Now if I logout from the authenticator ( whether I close the wallet tab or not ) , then log in with another user, say my User2, the available public IDs are still those of myUser1 when I reload the wallet page

Deleting the keys in localstorage fix it, and let me use myUser2 - I suppose localstorage should be erased when loging out from the authenticator / closing tabs . I had the same issue with the various apps that I created, and choose to use sessionstorage instead as a workaround, but this doesnā€™t help if the user opens a new tab. Iā€™d be glad to learn how you can fix that !

2 Likes
34

BUG: When trying to create lots of one type of coin, e.g. 10000000000000 gives a wallet value of 0.00000001
Probably need to cap the creation phase.

3 Likes
35

Very cool Seneca, great work

Public ID: mirror

6 Likes
36

Excellent news @Seneca, we are all looking forwards to have more things to experiment with. This is my id mytroons, and I created the troonsGold (with no issues) and this has to be called troons not the ones from @anon40790172 :smile: :smile:

7 Likes
37

Want some!! Or just sent me 0.00000001 troonsGold which we could call a ā€œIrvineā€ inspired by Bitcoinā€™s ā€œSatoshiā€ :wink: .

11 Likes
38

You just coined thatā€¦ SAFE 0.00000001 will now forever be called an irvine.

7 Likes
39

Just sent you a troonsGold ā€œIrvineā€:
safe://wallet.decorum/#/transaction/93d9ab28d63f7d090171abf54efc6ea75d0ea2691b591adbd03f82e1548810bb07b9000000000000012000000000000000975fdfc2ae3634fce08f5f728003c9caf2f2d9096f32961436f13863ffa3c1141800000000000000702801e4fc7f0000603301e4fc7f0000583301e4fc7f000000

I saw you sent me some troons too:
safe://wallet.decorum/#/set/1ed20ad43d153199dca4aed668e0ca773c0fb816793d6b1ebcfe092427e6398707b9000000000000012000000000000000502825300a2b7fcc417ef1e6c52b94181edf3210ad400e13d476bdf8b69c7ae41800000000000000702801e4fc7f0000183401e4fc7f0000783301e4fc7f000000

3 Likes
40

That is indeed an issue. We spotted it when testing too, and itā€™s something that we need to handle. I do not think the SAFE browser should clear the localstorage for you, but it might be an idea to have it stored per account. Anyway, we should add a logout function, or somehow detect another user is logged in and the previous session is outdated.

We experienced something similar during tests when we hit a 32 bit integer limit when encoding data. We fixed that, but now we still have a JavaScript limit which is about 53 bits. Weā€™re definitely aware of such limits, however, we decided they are at the moment not important enough to focus on.

9 Likes