Bitcoin Forum
October 09, 2024, 10:18:09 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 28, 2016, 07:14:08 PM
any updates?

Launch depends on public interest in this idea.

Go right ahead and spread the word!
2  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 10, 2016, 01:39:46 PM
This is considerably clearer, without getting complicated:

http://www.di.ens.fr/~cousot/AI/IntroAbsInt.html
3  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 10, 2016, 09:43:39 AM
Unclearly written, but relevant:

https://steemit.com/security/@dana-edwards/abstract-interpretation-and-how-to-write-secure-software
4  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 09:47:18 PM
#helloworld

https://twitter.com/KripkeSecure
5  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 09:22:33 PM
Dev, do u need a portuguese translation?

Pm me if u need this.
Cya

Thanks, we might. :-)
6  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 03:33:40 PM
I'll host a pool for it but please overthink about going with SHA256... There are so many nicer algos, fairer for GPU miners (including me Smiley)


Thanks, that's something to consider.

What algo's your favourite then?



How about Groestl or Myriad-Groestl... Or maybe Blake... Something modern at least

Not Keccak?
Also, I'm not so sure of the support, in rent-a-miner services, for those algos. Some people depend on that sort of thing.
7  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 02:57:27 PM
I'll host a pool for it but please overthink about going with SHA256... There are so many nicer algos, fairer for GPU miners (including me Smiley)


Thanks, that's something to consider.

What algo's your favourite then?

8  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 02:35:56 PM
Will there be translation bounties dev?

can you respond dev?

Thanks, I'll consider it.

Given the Chinese translation that @cyberhacker just did for us, I wonder if it'd be better to (a) translate and (b) mine early?
9  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 02:15:36 PM
I'll mine it, but I don't think I'll buy in the ICO, we'll see.

Doubt you will raise 2000 BTC without revealing identities. Good luck though.

I guess if people want it, it'll happen. :-)
10  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 01:50:38 PM
very interesting.

I am putting it into Chinese Blog http://btc12.com/2016/08/08/kripke-securesmartcontract/


Please consider it a translation with "red flag", cuz you guys are anonymous.


here is btt Chinese translation.

https://bitcointalk.org/index.php?topic=1579393.new#new



Thanks!
11  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 01:31:20 PM
min 2000BTC + anonymous? oh yeah  Roll Eyes

anonymous because of experimental nature? Care to expand this thought a bit?

We've seen many developers try something, have sentiment turn against them, and find their reputations wrecked.
This is in addition, and separate from, the possibility that this project could fail.
Finally we have real-world commitments that would be impacted by the sorts of knock-on effects that this community can cause.

Our value proposition is:
* we wanna do something to contribute to smart contract security.
* we have strong reasons to not trust Bitcointalk with our reputations.
* to do what's planned will take a lot of work. Having enough funding is necessary for the success of the project.
* we think we can give smart contracts in general, for the foreseeable future a means of being provably secure.
* this is your chance to be first to market with this tech.


(FYI we're not here to discuss this further. Take it or leave it.)
12  Alternate cryptocurrencies / Announcements (Altcoins) / Re: ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 12:49:10 PM
The Big Bang Theory's Kwipki ? Tongue

Kripke with rhotacism? ;-)

Either way, it's this guy:



13  Alternate cryptocurrencies / Announcements (Altcoins) / ANN [Kripke] Provably secure contracts; functional language; on-chain encryption on: August 08, 2016, 12:31:23 PM
Launch date TBC

//




kripke


n  |  “cryp-key”  |  \ krip-kē \



We* introduce Kripke, an exploration of "rigid designation" in the context of blockchain insecurity (specifically, malleability).


Problem description:
Smart contracts on Ethereum cannot be proven to be trustless. The Turing-completeness of Ethereum's scripting language makes it impossible to prove that a statement written in Solidity always returns the same result. Insecurity is a permanent feature of Solidity and any Turing-complete language.
We contrast this with Saul Kripke's notion of a "rigid designator," introduced in Naming and Necessity (1972):

A rigid designator designates the same object in all possible worlds in which that object exists and never designates anything else.


Intuitively, for smart contracts, rigid designation implies that a contract must be interpreted in exactly one way. As such, it completely avoids the insecurities of Bitcoin's malleability and Ethereum's inability to ensure determinate outcomes to contracts written in Solidity.



Thus we define the following features of Kripke-secure blockchains:


kripke-security

Kripke-security denotes security by virtue of determinacy of outcome. A statement in a given language is Kripke-secure if it designates rigidly, that is, it has exactly one meaning for all possible worlds.

A candidate technique for achieving Kripke-security is formal verification of (purely) functional language.


kripke-function

A Kripke-function has the same outcome in all possible worlds in which its semantics exist and never has any other outcome.

Obvious candidates for implementing Kripke-functions are functional languages (Haskell; Scala) with suitable type systems.


kripke-keystore

A Kripke-keystore is a system of Kripke-functions for the implementation of an encryption key storage facility on-chain.


kripke-contract

A Kripke-contract utilises only Kripke-functions, thus determining an entirely non-malleable outcome.


kripke-governance
Kripke-governance utilises only Kripke-contracts to determine provably trustless outcomes of social decisions, like voting or allocating funds.


//


coin specification

Concurrent POW/POS implementation
POW consensus algorithm: SHA256
Block time: ~10 minutes
Block reward to decrease in inverse proportion to difficulty
POS coin age maturation: 24 hours
Annual POS interest: 4%
Premine: 10 million, held by Foundation for ITO sale



project phases

Phase 1
Launch date: 20 Aug 2016
Blockchain inception
Mining begins
ICO funds mined at genesis block
Temporary use of stock PPC clone

Phase 2
ICO commences
Sale of 10 million tokens
Minimum amount to proceed to Phase 3: 2000 BTC

Phase 3
Kripke-secure development begins
Broad-based community collaboration, via Foundation contracts
Foundation to retain a portion of unsold ICO tokens to fund development (disbursed via contract)


references
http://langsec.org/    
https://en.wikipedia.org/wiki/Formal_methods    
http://plato.stanford.edu/entries/rigid-designators/    
http://plato.stanford.edu/entries/possible-worlds/
https://en.wikipedia.org/wiki/Chomsky_hierarchy


*Due to the experimental nature of this project, and due to its potential to impact upon our public identities and employment, we choose to remain anonymous for the time being.


Please note: this project is strictly experimental in nature and is not "currency" or "property". Additionally, the project may fail, or fail to attract sufficient support. Its purpose is solely to explore the potential of rigid designation to secure smart contracts.


Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!