[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 561.

prix

hero member

Activity: 750

Merit: 511

Quote from: coinsolidation on July 10, 2014, 03:44:38 AM

Use localStorage in the browser, this is a reasonable solution which requires no usage of cookies. The passphrase is stored in the users local browser.

LocalStorage is replacement for Cookie. It's not safe. You can read the content of localStorage by using third-party local program or manual using browser tools.
Can you tell exactly how Ripple uses the localStorage?

KLONE::Vader

member

Activity: 89

Merit: 10

Bter volume 81 BTC... wow

tobeaj2mer01

legendary

Activity: 1098

Merit: 1000

Angel investor.

Quote from: SyRenity on July 10, 2014, 02:37:10 AM

Quote from: bitcoinpaul on July 10, 2014, 02:28:18 AM

Why did you start already?

https://bter.com/trade/crsale_btc

As explained earlier, it appears that Bter missed our notification to push the sale 24 hours and went with it on last night 00:00 UTC, rather then today 00:00 UTC.

We still will stick to the original plan and count the 30% bonus starting today 00:00 UTC.

What do you mean, what about the raised BTC in bter until now, is there any bonus? I have been following this thread and know it had started from the posts this morning.

KLONE::Vader

member

Activity: 89

Merit: 10

Quote from: crypti on July 10, 2014, 03:39:40 AM

3. About fees read first post. Fees decreases with each increasing amounts volume

Do fees also increase with each decreasing amounts volume?

crypti

hero member

Activity: 511

Merit: 500

Boris, Crypti Lead Developer, Lisk Advisor

Quote from: coinsolidation on July 10, 2014, 03:44:38 AM

Quote from: crypti on July 10, 2014, 03:39:40 AM

Quote from: jokumat on July 10, 2014, 03:33:16 AM

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

1. We can't, because in this way we need to store your passphrase in cookie browser. It's dangerous. Every transaction need sign.

You can.

Use localStorage in the browser, this is a reasonable solution which requires no usage of cookies. The passphrase is stored in the users local browser. You may want to wrap it so that a traditional username and password creates the key which is used as the passphrase. Use Public key cryptography for this.

It is an existing proven approach, look at how ripple has implemented it.

I wish for your users this had been discussed and asked before going live.

Localstorage dangerous too, all you passphrases will be stored in your browser.
Passphrase create public and private key. We can try to save passphrase in memory, then create something like session.
But we need to see how far it is safe.

coinsolidation

sr. member

Activity: 294

Merit: 250

Bitmark Developer

Quote from: crypti on July 10, 2014, 03:39:40 AM

Quote from: jokumat on July 10, 2014, 03:33:16 AM

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

1. We can't, because in this way we need to store your passphrase in cookie browser. It's dangerous. Every transaction need sign.

You can.

Use localStorage in the browser, this is a reasonable solution which requires no usage of cookies. The passphrase is stored in the users local browser. You may want to wrap it so that a traditional username and password creates the key which is used as the passphrase. Use Public key cryptography for this.

It is an existing proven approach, look at how ripple has implemented it.

I wish for your users this had been discussed and asked before going live.

crypti

hero member

Activity: 511

Merit: 500

Boris, Crypti Lead Developer, Lisk Advisor

Quote from: jokumat on July 10, 2014, 03:33:16 AM

I tried beta web wallet. Seems to be working, incredibly fast and smooth. But with real transaction fees sending cryptsi will be much less fun Sad

questions:

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

2. web wallet should be https

1. We can't, because in this way we need to store your passphrase in cookie browser. It's dangerous. Every transaction need sign.
2. Yes, we will add SSL today.

3. About fees read first post. Fees decreases with each increasing amounts volume

prix

hero member

Activity: 750

Merit: 511

Quote from: jokumat on July 10, 2014, 03:33:16 AM

I tried beta web wallet. Seems to be working, incredibly fast and smooth. But with real transaction fees sending cryptsi will be much less fun Sad

questions:

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

2. web wallet should be https

1. What is problem with it? They can't save your password it's not safe. As example all my important wallets is encrypted and I use a password any time when I send money. Use KeePass or something for password managing.

2.

Quote from: crypti on July 10, 2014, 02:02:49 AM

Today will be update:
- Ledger.
- OpenSSL for wallet.
- Fixes in UI.

mydearvoice

sr. member

Activity: 250

Merit: 250

I just want to laugh out loud, I want to look at investors lose money.

coinsolidation

sr. member

Activity: 294

Merit: 250

Bitmark Developer

Quote from: jokumat on July 10, 2014, 03:33:16 AM

2. web wallet should be https

This is a MUST.

If there is a web wallet which is not https, take it down and move it to https immediately.

jokumat

sr. member

Activity: 249

Merit: 250

I tried beta web wallet. Seems to be working, incredibly fast and smooth. But with real transaction fees sending cryptsi will be much less fun Sad

questions:

1. You can't expect users to write 100+ characters each time they pay (authorising each transaction individually).

2. web wallet should be https

xalbex

newbie

Activity: 6

Merit: 0

After the release of crypti, developers should buy it with the accumulated funds. In this way, their reward will be connected to the success of the coin. Immediately there will be a safe market capitalization for the coin. New investors will be attracted even after the release of the coin.
Crypti will make success more easily!

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: S3MKi on July 10, 2014, 02:17:30 AM

bought some crsale on bter.

Appreciate your patronage!

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: bitcoinpaul on July 10, 2014, 02:28:18 AM

Why did you start already?

https://bter.com/trade/crsale_btc

As explained earlier, it appears that Bter missed our notification to push the sale 24 hours and went with it on last night 00:00 UTC, rather then today 00:00 UTC.

We still will stick to the original plan and count the 30% bonus starting today 00:00 UTC.

SyRenity

hero member

Activity: 756

Merit: 502

Quote from: ?? on ??

Quote from: SyRenity on July 10, 2014, 02:09:01 AM

Having two different escrow channels, I don't expect we will introduce a direct one as it will both complicate post-presale calculations and cause some wariness in the community.

Sounds reasonable... but you still need to come out with a definitive NO then (as opposed to don't expect we will introduce) and make sure you stick to it! Wink

Let's do like this, if we do introduce the direct channel (pending demand of at least 20 buyers to make it worthwhile), we will compensate your 1% when issuing Crypti.

Deal?

bitcoinpaul

hero member

Activity: 910

Merit: 1000

Why did you start already?

https://bter.com/trade/crsale_btc

prix

hero member

Activity: 750

Merit: 511

Quote from: crypti on July 10, 2014, 02:16:08 AM

Nxt was builded. JS can't be builded.

What do you mean? The only difference is the moment of compile. Java is compiled once, JS - during execution (both using JIT).
But it bears no relation to obfuscation.

S3MKi

legendary

Activity: 1540

Merit: 1016

bought some crsale on bter.

crypti

hero member

Activity: 511

Merit: 500

Boris, Crypti Lead Developer, Lisk Advisor

Quote from: prix on July 10, 2014, 02:11:13 AM

Quote from: SyRenity on July 10, 2014, 01:59:05 AM

I'm aware of it, and you could actually try to do the same with Crypti code, once the Crypti node is released to download after the pre-sale ends.

NXT is not obfuscated, Crypti and Qora is obfuscated on start. It's not same. NXT is open source in fact, others two - not.
This is for clarity only. I am not against obfuscation.

Quote

Source will be published in 3 month after release. Before it will be just js obfuscated code.

Nxt was builded. JS can't be builded.

prix

hero member

Activity: 750

Merit: 511

Quote from: SyRenity on July 10, 2014, 01:59:05 AM

I'm aware of it, and you could actually try to do the same with Crypti code, once the Crypti node is released to download after the pre-sale ends.

NXT is not obfuscated, Crypti and Qora is obfuscated on start. It's not same. NXT is open source in fact, others two - not.
This is for clarity only. I am not against obfuscation.

Quote

Source will be published in 3 month after release. Before it will be just js obfuscated code.

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 561. (Read 804701 times)