Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
buckie
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
31.
▲
by
buckie
9y ago
Why bad timing? This is really just an example that while safe smart contracts are technically possible using Solidity/EVM, it's practically impossible. "One of the best Solidity devs" just failed to write a safe contrac
32.
▲
by
buckie
9y ago
It's closest to the middle, assuming that you meant that you're stating the properties that you want to test. It does more than that, but at its base that's effectively how it works so it's close enough for a solid intui
33.
▲
by
buckie
9y ago
> Not just proof of "design", but proof of the implementation. Absolutely, few people really get this. Even those that do get it generally don't know what it looks like in practice because it's so rare. In case you&
34.
▲
by
buckie
9y ago
I think this is the problem or at least what permits what we're seeing. If coin holders had to choose a side for their coins to be found on I bet things would be rather different. However, this is in no one's financial interest. R
35.
▲
by
buckie
9y ago
I think they mean that a blockchain doesn't exist in a vacuum, someone has to write the code. While anyone can write a new client/protocol upgrade people won't upgrade to just anyone's new client given how much value Bit
36.
▲
by
buckie
9y ago
> A contract language has nothing to do with blockchains. In a strict sense, you're right. All a smart contract language needs to run is a linear set of inputs. However, they have a lot less utility without the other parts of a bloc
37.
▲
by
buckie
9y ago
If you're thinking about the EVM's take what smart contracts should look like then you're 100% right. General, replicated computation is a good first step but a poor idea long term. Blockchains, both public and private, are r
38.
▲
by
buckie
9y ago
tl;dr -- private blockchains make it possible to distribute a common piece of infrastructure between businesses with competing interests. The sit between the stream of new inputs and the database. I've built one of these types of syste
39.
▲
by
buckie
9y ago
I'm pretty sure they are JetCat RC engines (based on the purple cowling): http://www.dreamworksrc.com/catalog/Jetcat-Engines
40.
▲
by
buckie
10y ago
Nothing. I honestly have no idea what they're talking about. Haskell apps tend to be tanks once they're deployed. The only issue I've ever seen was a Haskell app getting OOMed because the dev box only had 8GB of RAM and someo
41.
▲
by
buckie
10y ago
While I agree that it's possible to write maintainable in kdb+, I'd argue that it takes noticeably more effort; or, as in inverse, if you drop your coding standards things get worse faster. I'd say the same for regex as well
42.
▲
by
buckie
10y ago
In my experience, kdb+'s k and q (which is broadly speaking a legibility wrapper around k, which again broadly speaking is APL without unicode) are phenomenally fast for dense time series datasets. Though they can struggle (relatively,
43.
▲
by
buckie
10y ago
Also, `ByteString` as the qualified name is a bit unusual but it probably is helpful for clarifying what's going on for people unfamiliar with Haskell. I'm more used to seeing: import Data.ByteString (ByteString) import
44.
▲
Evolution of Kadena, the First Real Private Blockchain
(coindesk.com)
2 points
by
buckie
10y ago
|
0 comments
45.
▲
by
buckie
10y ago
> People who grew up in one state, went to college in another and then moved somewhere else are counted as migrating from the state where they attended college. I suspect that may have something to do with it. Maybe Vermont has more init
46.
▲
by
buckie
10y ago
Maybe, our system gets 8k-12k transactions per second with full replication + crypto up to a few thousand consensus nodes (slows down around 4k nodes). That type of performance opens up a lot of potential applications. As for "a horsel
47.
▲
by
buckie
10y ago
I did, though I can't edit it now sadly. And it's not that TLS isn't secure but about what features TLS gives the system. The gist of this is that TLS doesn't give one a durable/persistable form of security vs ppk-s
48.
▲
by
buckie
10y ago
Pact[1], the language we've built, has the idea of an `admin keyset` that enables admins with the right number of signatures from the right number of keys to migrate contracts. Our approach is rather different from the EVM's as sm
49.
▲
by
buckie
10y ago
I'd say there are a few ways to think about blockchain's utility in private contexts (public chains are pretty different because of their ability to allow for anonymous participation). The two best ones are the intra- and inter-or
50.
▲
by
buckie
10y ago
Smart contracts definitely have a tradeoff between new toolset/languages vs infrastructure level features. With smart contracts, anyone can write code for the chain vs the "write your application to be deterministic" approach
51.
▲
by
buckie
10y ago
I can't say I'm all that surprised. R3 serves as both an R&D lab and a place to connect vendors and potential clients. Moreover, the focus is on private/permissioned blockchain tech. The tech in this space is still quite
52.
▲
Open-Sourcing the Pact Smart Contract Language
(kadena.io)
1 points
by
buckie
10y ago
|
0 comments
53.
▲
Why Business Rules Will Dramatically Expand the Impact of Blockchain
(forbes.com)
3 points
by
buckie
10y ago
|
0 comments
54.
▲
Show HN: Pact – a safe smart contract language (web editor)
(kadena.io)
18 points
by
buckie
10y ago
|
2 comments
55.
▲
Mining and private blockchains don't mix
(kadena.io)
3 points
by
buckie
10y ago
|
0 comments
56.
▲
Confidentiality in Private Blockchains [pdf]
(kadena.io)
2 points
by
buckie
10y ago
|
0 comments
57.
▲
by
buckie
10y ago
Well, it depends what you really want out of the system. I'd argue that generalized computation is inappropriate for a permissioned blockchain. For a public blockchain, sure, though I'd still not go with Ethereum for a bunch of re
58.
▲
by
buckie
10y ago
Of course. If Bitcoin dropped the number of transactions per block to 1 tomorrow would it stop being a blockchain?
59.
▲
by
buckie
10y ago
For the case(s) you've mentioned, you are correct: the state that is built up disappears on error. However, when last I checked, there are several operations that fall outside of this guarantee, e.g. new account creation, that are not
60.
▲
by
buckie
10y ago
Yeah, sounds interesting. Ping us at info@kadena.io so we can chat more/keep in touch. Pact should be O/S Sunday or Monday, we're putting the finishing touches on the web editor now and the Atom plugin is already out there[1]
More ›