Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - roadscape

Pages: 1 [2] 3 4 5 6 7 8 9 ... 64
16
General Discussion / Re: Does BTS suffer from the same Ethereum paradox or does stealth conquer it?
« on: April 19, 2016, 11:40:10 pm »
Depending on how blind balances/transfers were implemented, this would be pretty easy to do with external (3rd party) orderbooks while keeping the act of exchanging the assets private & trust-free. Practically speaking, probably the biggest whale would be the one hosting/securing the orderbook. The trades could be initiated on an external server using proposed transactions. And there would still be a public orderbook for the less privileged. :)

17
General Discussion / Re: Cryptofresh API
« on: April 19, 2016, 11:26:46 pm »
Thanks @bang-king  :) I haven't had a chance to mess around with any web wallet code yet, not sure what the learning curve is like! But I would enjoy such a project.

Quote from: paliboy on April 15, 2016, 01:02:38 pm
Quote from: roadscape on April 07, 2016, 03:25:32 pm
Thanks, any specific API's you like to see added??

API for order book of various traiding pairs would be awesome.

Do you need orders or just depth? I added a depth API recently but haven't documented it yet:
https://cryptofresh.com/api/market/depth?pair=BTS_USD

Quote from: jabbajabbaつ◕_◕つ on April 15, 2016, 03:45:05 pm
Would be nice i you could add 24 hour statistics like...
users registered, bts volume traded,  assets created, transactions processes etc...

Great ideas.. I will include these "quick stats" as I tidy up the front page

Quote from: dannotestein on April 15, 2016, 03:39:20 pm
A moving average would be nice for the charts to show long term trends

Are you referring to price charts, operation-types charts, or both?

18
General Discussion / Re: Poor Man's Patent
« on: April 19, 2016, 11:12:08 pm »
Are you looking for a web app that private/securely stores PDF files but publishes their hashes publicly?

19
Random Discussion / Re: The Problem with the Crypto Debate
« on: April 19, 2016, 11:04:21 pm »
This was an insightful read.. useful points and balanced reasoning.. thanks!

20
Random Discussion / Re: Tribute to the Greeeeat Tony "the Tiger" K
« on: April 19, 2016, 11:00:07 pm »
lmao

21
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: April 19, 2016, 10:44:24 pm »
Quote from: tbone on April 15, 2016, 06:00:51 pm
A trend that would be great to visualize and follow is total value transacted on the DEX (excluding transfers).  So if you can put that on the daily chart, it would certainly be appreciated!

I do like this suggestion, and it will be easy to do once I implement the next stage of tracking market data.

There are a still a few questions though, and they tie into numerous other features:
 - What units should "total volume" be in? (it should be relatively future-proof)
 - How do we draw the line between high confidence and low confidence volume figures? See https://cryptofresh.com/assets -- do we include TRUMP, and BTCPLUS? I created an algorithm that was effective for a time, but I've since had to blacklist some assets from the charts. Perhaps it's best to create a whitelist, but that requires ongoing maintenance and.. *shudder*.. politics.
 - How do we obtain the most accurate price for an asset A in terms of any given asset B?
  What's a CLINTON worth? https://cryptofresh.com/a/CLINTON
  What's a BTCPLUS worth? https://cryptofresh.com/a/BTCPLUS - $233, $0.384, or $229?
  (it could be volume-weighed, but over what time period? perhaps it needs to volume-weighed and also using EMA avg for each pair...)

It's possible to do something relatively quick just for this case (getting a line on a graph) but these questions will continue coming up as I get deeper into the market data. Many requested/planned features depend on a set of solid solutions here. These questions, and the application of their answers, is something to which I would want to dedicate at LEAST 1-2 weeks of my time.  But I'm definitely thinking about it (and a lot of other feature requests from everyone I haven't been able to address yett.. I haven't forgotten!! just takes time..)

TLDR - I very much want this feature but I see it as a small part of a bigger project.

22
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: April 14, 2016, 09:37:02 pm »
I've been reconsidering priorities and I'd like to submit a slight change of plans:

Worker:
 - I'm not going to wait until the worker is fully funded to release the code. Instead, that's where I'd like to shift my immediate focus -- documenting & releasing the source. To set it free, allow it to be reused, and help others get involved.
 - Besides that, the next tasks remain: internationalization, page updates, and as always.. more DEX data.
 - No change in my commitment to keep building/improving cryptofresh while my worker is active.
 - No immediate plans to launch another worker after this one expires (May 31), but I will continue to support cryptofresh.

Witness:
 - I rescind my witness resignation and will resume publishing feeds.
 - I also intend to run for a Steem witness position.

I'm glad I held off on the "blockchain social network" aspect of this worker proposal and focused on DEX-specific features! However that aspect is still something I'm very passionate about, and that's why I'm excited about Steem's approach. That being said, I still believe BitShares could benefit greatly from a blockchain-based trollbox and announcement channel (and I'd be happy to work with @svk to add it to the wallet if he has time & the stakeholders still consider it a priority). I'm just going to scrap the threaded discussion and tipping features for now.

Next week I will be taking a break from cryptofresh duties to catch my breath and get witnesses/servers set up properly. Over the following 1-2 weeks I will document & prepare the code for release, and then switch back to completing features. After May 31 I'll make sure cryptofresh continues to run smoothly and be a useful resource. There's still a *lot* more I'd like to do with cryptofresh but need to let the dust settle.

Feedback/questions welcome!

23
General Discussion / Re: [ANN - AMA] bitCash - Digital Money of the Future!
« on: April 13, 2016, 09:26:55 pm »
I briefly checked it out yesterday it's a great start! Truly minimalistic. The weird thing is that the simplicity was almost confusing. Maybe that's just me being used to our wallets :) But an extra option or two, table column, or a little bit more info somehow could help. Maybe some guidance text, especially on the account create page. Small things like: "Enter first name" could be "Enter nickname" because it communicates the intent better. Some other brief thoughts:
 - There are 2 white dots above and below the $ sign, they might look ok if they were aligned with the center stroke but they are offset to the right by a few pixels in my browser
 - The ">" and "<" buttons would be better as unique icons or maybe simply flipped. On the "Send" page the arrow points to the right, which makes me think "go forward" when it really brings me back to the account overview.

I haven't tried making a transaction yet.. it doesn't recognize assets other than CASH.USD right? Do we have a USD:CASH.USD market?

24
General Discussion / Re: [ANN] Peermit 2-Factor-Authentication deployed in the TESTNET!
« on: April 12, 2016, 05:18:00 pm »
Quote from: xeroc on April 11, 2016, 02:03:20 pm
Quote
2016-04-11 13:18:20,068 - monitor - WARNING - 1.10.68: Our approval required but we don't know user lock-it-down (1.2.463)
Have you added your mail address and clicked the "register" button?

Yes, it gives the message "Successfully updated your settings: Registered". I'm testing with a sharklasers.com email address.

25
General Discussion / Re: [ANN] Peermit 2-Factor-Authentication deployed in the TESTNET!
« on: April 11, 2016, 01:22:02 pm »
Quote from: xeroc on April 11, 2016, 01:07:36 pm
Quote from: roadscape on April 11, 2016, 01:00:55 pm
Built into the wallet now.. nice!! +5%

I tried to propose a tx, but I get: "Missing Active Authority 1.2.463". Strange, 1.2.463 is the account I just created (lock-it-down). I did verify that I have a 2nd authority and the threshold is 2.
You need to propose a transfer from ANOTHER account.
Also note that you have not added a reference account to your lock-it-down account.

This account shows you how things should be looking (take a look at the ACTIVE permissions tab):
https://testnet.bitshares.eu/#/account/tesaf11/permissions/

I will work on making it more clear that

a) you need a regular account as reference that can create proposals for the secured account and
b) you need to have the reference account added to your active permissions .. which is what step 2 in 2FA does

Ok, now I was successfully able to propose a transaction, but I don't see an email yet. (`roadscape` proposed for `lock-it-down` to send 10,000 TEST to `faucet`)

26
General Discussion / Re: [ANN] Peermit 2-Factor-Authentication deployed in the TESTNET!
« on: April 11, 2016, 01:00:55 pm »
Built into the wallet now.. nice!! +5%

I tried to propose a tx, but I get: "Missing Active Authority 1.2.463". Strange, 1.2.463 is the account I just created (lock-it-down). I did verify that I have a 2nd authority and the threshold is 2.

27
General Discussion / Re: STEALTH Status Update
« on: April 11, 2016, 03:27:18 am »
Quote from: gamey on April 11, 2016, 01:57:03 am
Quote from: Thom on April 11, 2016, 01:28:31 am
You are correct on both counts tbone. @Erlich Bachman - allowing short or insecure keys isn't an option for anyone. The last thing BitShares needs is someone loosing their life savings b/c they failed to provide a good brain key.

I got a lot out of BM's discussion on last Friday's mumble. Two important points:

1) There are higher risks for putting wallets on the blockchain, significantly b/c attackers can hammer their target trying to crack the password without any delays between each attempt. They could employ many computers in parallel in the attempt also.You might be surprised at how quickly a password can be guessed via brute force means like that.

2) It's not sufficient to only save private keys. That could work if you're saving a BitShares wallet with only standard accounts, but not if the wallet contains stealth addresses. And, unless a limit is put on how many accounts and stealth accounts a wallet may contain the size of the backup could get prohibitively large to store on the blockchain, even without transaction history.

Regarding the use of blinded transfers as a replacement, I'm not a big fan of that approach. I would want to see more details about the viability of that, focused on the time required to implement it, what the exposure it has on existing code to new bugs, both front end and backend, not to mention who will implement it with this no-dilution cloud hanging overhead.

It is worse than #1. They can store the hashes and then clear out any account that goes forward and uses that hash. With 5 TB drives costing so cheap, you can create really really big hash stores .  So as soon as any transaction hits the network, this actor looks up their list of hashes and sees if it is crackable.

If there's a server containing a bunch of crypto wallets the only safe assumption to make is that it will be hacked. So they better be very resistant to brute forcing either way imo. If you're describing rainbow tables, salting helps prevent those types of lookups.

28
General Discussion / Re: Cryptofresh Block Explorer + MUSE now available
« on: April 07, 2016, 11:28:08 pm »
Latest UI updates:
https://cryptofresh.com/charts
https://cryptofresh.com/u/stealth-mgmt
https://cryptofresh.com/a/USD

29
General Discussion / Re: STEALTH Status Update
« on: April 07, 2016, 11:14:52 pm »
Quote from: Shentist on April 07, 2016, 06:24:49 pm
Quote from: kenCode on April 07, 2016, 06:11:42 pm
Quote from: roadscape on April 05, 2016, 03:27:11 pm
Quote from: bytemaster on April 04, 2016, 05:33:54 pm
The server-side wallet storage was not part of the proposal, but something we felt was necessary to backup/secure user funds. We do not yet have confidence in the reliability of server-side storage to enable this feature. There is a significant about of liability associated in offering to host/backup user wallets.  We don't want to be responsible for the loss of funds.

Why not backup wallets directly on the blockchain? Along with a hash of the owner's email for easy lookups later. And maybe some random noise.

 +5% +5% +5% +5% +5% +5% +5% +5%
Forget servers, we have a blockchain!
 
How about this...
Throw a bunch of different random numbers and other noise (maybe even the brainkey too?) into a json file, then compress it, encrypt it, base58 encode it, and throw that single text string into a memo. then, there is your backup. just call it up via wif, throw your key at it, and voila'... would that work? It would only cost a few BTS to store it as a transaction in a block too (for LTM's of course). For extra security, make a second backup. Yes? No? Horrible idea?
 
Hiring (and having to constantly trust) a backup server company is a huge expense and risk that Bitshares' name does not need. I think we should leverage the tools that we already have as much as possible. We have the most scalable chain on earth, let's really show it off!

this would be awsome!

how likely is it, that someone could entcode my password?

We would have to use very secure passwords.. maybe encrypt the wallet using its own brain key. That would make it easy to recover and hard to hack.. isn't this effectively a brain wallet?

30
Stakeholder Proposals / Re: [Worker Proposal] Blockchain Explorer and API Development
« on: April 07, 2016, 04:41:48 pm »
Last week was backend work and initial API release.

This week I've focused on view internationalization, refactoring, and visual cleanup of the account and asset pages. These tasks go nicely together and give me a chance to comb over each page. It's a work in progress but I'll release some of the GUI changes today. Within 2 weeks I expect to have Chinese version of the site 80% done and ready for testing. During that period there will also be updates to the home page (more charts and less lists), and possibly the asset/market pages.

Pages: 1 [2] 3 4 5 6 7 8 9 ... 64

Page created in 0.027 seconds with 23 queries.