Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jude-
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
56 ms
·
481.
▲
by
jude-
7y ago
I never claimed otherwise ;) However, I will claim that the lower operational expenditure (and lower liability for holding user data) makes profitability on-the-whole easier to achieve in Blockstack-powered apps.
482.
▲
by
jude-
7y ago
The operational costs are considerably lower with Blockstack, since the app doesn't host any user state (and in many cases, no state at all). Most apps don't need a database of any kind -- all the business logic runs client-side
483.
▲
by
jude-
7y ago
Blockstack engineer here. The protocols under the hood ensure that each user chooses where their data gets stored -- all that's required is that wherever it is, it's available via HTTP(s) so it can be loaded into your Web browser.
484.
▲
by
jude-
7y ago
Core platform developer here (for 4+ years). Would absolutely work on this project in my spare time if I wasn't already employed at Blockstack PBC. You can also check our various projects' contributor graphs on Github (all under
485.
▲
by
jude-
8y ago
So filecoin would just be a slower, less scalable, and more costly way to pay for S3?
486.
▲
by
jude-
8y ago
What stops a filecoin miner from storing all replicas to S3? If nothing, then why use filecoin at all? Economies of scale would dictate that the most successful filecoin miners would simply be cloud storage providers by another name (but
487.
▲
by
jude-
8y ago
Blockstack engineer here. AFAIK Graphite Publishing will make your files accessible as URLs under graphitedocs.com, but since the code is open [1], you could run an instance on your own domain. [1] https://github.com/graphi
488.
▲
by
jude-
8y ago
Blockstack engineer here. Your points are well-taken, and are straightforward to address. Blockstack uses a storage system called Gaia, which in a nutshell acts as an overlay on top of existing commodity storage systems (including cloud st
489.
▲
by
jude-
8y ago
Blockstack engineer here. Your Blockstack ID is anchored to the Bitcoin blockchain, so everyone else can find (1) your public key and (2) the location(s) where your profile and application data are stored. The naming system is described he
490.
▲
by
jude-
8y ago
I agree. This is also why Blockstack isn't built on IPFS -- your data is only available as long as someone's pinned it. Gaia (the Blockstack storage system) will let you use IPFS as your backing store, but at the end of the day i
491.
▲
by
jude-
8y ago
Blockstack engineer here. The user pays for their storage -- you would supply your own space on a storage provider of your choice (be it a cloud storage provider, your server, a BitTorrent swarm, etc.), and use it as a back-end to your Gai
492.
▲
by
jude-
8y ago
> AFAICT, You can't use the platform without authenticating to the centralized servers of blockstack Nope, this is not true. You can authenticate to an application without a Blockstack Core node; the only thing the Blockstack Core
493.
▲
by
jude-
8y ago
Blockstack engineer here. Curious what makes you say our solution is DOA? Anyone can register a username with a Bitcoin transaction or two, and anyone can run a Gaia hub of their own. Blockstack PBC provides defaults to help users get st
494.
▲
by
jude-
9y ago
Blockstack engineer here. Just want to clarify for other readers that Blockstack Core has a "fast-sync" mode that lets you spin up a full node in a minute or two. The downside is that it uses a recent signed snapshot from Blocks
495.
▲
by
jude-
9y ago
> But you can reason about what any possible transaction can do by reasoning about all possible inputs to your code; you don't need to know anything about how other contracts were written, since even if they are formally provable, t
496.
▲
by
jude-
9y ago
Parent said "Neither of those limits actually makes solving the problem feasible in practice." This is correct, since the input space is too huge to feasibly explore. Yes, it is technically correct that there are a finite number
497.
▲
by
jude-
9y ago
I want to know what any possible transaction can do. See my sibling comments.
498.
▲
by
jude-
9y ago
Pretty sure the parent was saying the opposite. Testing every possible input is infeasible, since the number of possible inputs (and number of possible states) is HUGE.
499.
▲
by
jude-
9y ago
That's much easier said than done. If formal methods were practical, we'd be using them already everywhere else.
500.
▲
by
jude-
9y ago
Because in practice, I'm trying to reason about the consequences of submitting a given transaction. A transaction can invoke many smart contracts in addition to mine. It's not enough for my code to be correct; every piece of cod
501.
▲
by
jude-
9y ago
> While others have pointed out that this is wrong, it's worth amplifying: Turing machines are deterministic. You can run the contract locally and observe how it behaves, and it will behave the same way in the same environment elsew
502.
▲
by
jude-
9y ago
Sorry, I didn't qualify "always feasible" well enough. What I meant was, I want it to be feasible to reason about the halting states of every single smart-contract that will ever interact with my code. Not just the ones t
503.
▲
by
jude-
9y ago
> This comment is simply incorrect. The gas limits do make smart contracts decidable. It is a mathematical fact. This line of reasoning does not help me write better code, and does not address the parent's concerns. Using this argu
504.
▲
by
jude-
10y ago
You might want to take a look at Blockstack ( https://blockstack.org/ ). It does exactly this on top of the Bitcoin blockchain. You resolve a globally-unique name to a DNS zone file, which has URI resource records to off-ch
505.
▲
by
jude-
10y ago
Nope, it applies to every person within the US. The Bill of Rights does not even contain the word "citizen." Moreover, the SCOTUS has ruled multiple times [1] that every person in the US--illegally or not--is entitled to due pro
506.
▲
by
jude-
10y ago
> It seems like we have a quite different understanding how DHTs are used, probably shaped by different use-cases. Let me see if I can summarize yours correctly: a) over time nodes will be interested or have visited in a large proportion
507.
▲
by
jude-
10y ago
> This is usually considered too expensive in the context of non-coin/-blockchain p2p networks because you want nodes to be able to run on embedded and other resource-constrained devices. The O(log n) node state and bootstrap cost l
508.
▲
by
jude-
10y ago
> But then you are running a private tracker for personal/closed group use and have a trust source. If you have a trust source you could also run a closed DHT. But the bittorrent DHT is public infrastructure and best compared to pub
509.
▲
by
jude-
10y ago
> In practice trackers do divulge all the same information that can be gleaned from the DHT and so does PEX in a bittorrent swarm. Those are far more convenient to harvest. I'm confused. I can configure a tracker to only communicat
510.
▲
by
jude-
10y ago
S/Kademlia does not solve this problem; it simply slows down the rate at which an adversary can attack the system by a small amount (i.e. by making node ID creation more expensive and increasing a key/value pair's number of r
More ›