Search content
Sort by

Showing 5 of 5 results by operezm
Post
Topic
Board Legal
Topic OP
Bitcoin ECDSA patent infringement?
by
operezm
on 22/04/2015, 21:37:18 UTC
I work for a Tech company and when we're deciding whether or not to use ECDSA found in OpenSSL for one of our new projects, the legal guy told us we couldn't use ECDSA from OpenSSL because, it contains ECC code that is patented by Certicom.

I did some searching and I did find that Certicom holds around 130 patents in the Elliptic Curve Cryptography area and that patented code is indeed in OpenSSL.

Questions:

Is Bitcoin infringing these patents? 

How about other people creating Apps for Bitcoin that use ECDSA?
 
Post
Topic
Board Bitcoin Discussion
Re: Gavin reveals Satoshi's been secretly working on BTC 2.0
by
operezm
on 01/04/2015, 04:09:01 UTC
I like this part  Cheesy

Quote
Gavin: If I were Satoshi, I wouldn't be here talking to you, I'd be in Bahamas sipping Piña Coladas...

It is good to see these people do pay attention to the real innovation being brought by the altcoins.

Post
Topic
Board Altcoin Discussion
Re: Most undervalued coin?
by
operezm
on 27/03/2015, 17:07:51 UTC
If you are looking for a truly undervalued/sleeping coin, you should take a look at Kryptohash (KHC)

It is a pure 100% PoW coin just like Bitcoin but, Kryptohash has features that makes it really unique.

It is the only cryptocoin to date that uses 320bit hashes.  

It has a new PoW algorithm called KSHAKE320 that prevents ASIC/FPGA rape that affects most of the PoW coins.  This algorithm was recently upgraded to version 2 to make it even harder for ASIC/FPGA vendors to enter this market.

It uses ed25519 for digital signatures and PID algorithm that keeps the network difficulty spot on

Also, if you look at KHC closely, you'd notice that satoshi-wise KHC is 1000 times less inflationary than BTC.  

  1 BTC = 100,000,000 satoshis
  1 KHC =       100,000 kryptoha-toshis


Post
Topic
Board Development & Technical Discussion
Re: Building headless Bitcoin and Bitcoin-qt on Windows
by
operezm
on 20/04/2014, 21:45:15 UTC
@operezm, I still haven't figured it out. Adding the library and include folders of leveldb in the GCC specs file did not help either.

Could anyone explain the error format to me? It seems confusing.

Hi Jori,

I ended up deploying a fresh Win7 Pro 32bit Virtual Machine, followed the OP instructions to the letter and I was able to link it properly this time. 

Post
Topic
Board Development & Technical Discussion
Re: Building headless Bitcoin and Bitcoin-qt on Windows
by
operezm
on 20/04/2014, 00:33:48 UTC
I followed this guide loosely and successfully compiled OpenSSL, BDB and Boost (compiling for the headless version, so no QT, protoc, libpng or qrencode needed). Then I set the appropriate include and library files in the gcc specs file, so that they could be found and ran autogen.sh and configure. All went well and a makefile was generated in the root directory, which I ran. It compiled all modules successfully and then tried to build bitcoind (I believe), outputting:

Code:
Making all in src
make[1]: Entering directory `/i/code/bitcoin_git/bitcoin/src'
make  all-recursive
make[2]: Entering directory `/i/code/bitcoin_git/bitcoin/src'
Making all in .
make[3]: Entering directory `/i/code/bitcoin_git/bitcoin/src'
  CXXLD  bitcoind.exe

This failed however with a host of errors (I included the head only, but I think the problem can be derived from this, as the other errors are very alike):

Code:
libbitcoin_server.a(main.o): In function `CLevelDBBatch':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::WriteBatch()'
libbitcoin_server.a(main.o): In function `~CLevelDBBatch':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
libbitcoin_server.a(leveldbwrapper.o): In function `Z11HandleErrorRKN7leveldb6StatusE':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:18: undefined reference to `leveldb::Status::ToString() const'
libbitcoin_server.a(leveldbwrapper.o): In function `ZN15CLevelDBWrapperC2ERKN5boost10filesystem4pathEjbb':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:38: undefined reference to `leveldb::Options::Options()'
libbitcoin_server.a(leveldbwrapper.o): In function `GetOptions':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:29: undefined reference to `leveldb::Options::Options()'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:30: undefined reference to `leveldb::NewLRUCache(unsigned int)'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:32: undefined reference to `leveldb::NewBloomFilterPolicy(int)'
libbitcoin_server.a(leveldbwrapper.o): In function `ZN15CLevelDBWrapperC2ERKN5boost10filesystem4pathEjbb':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:52: undefined reference to `leveldb::DestroyDB(std::string const&, leveldb::Options const&)'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:57: undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::string const&, leveldb::DB**)'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.cpp:47: undefined reference to `leveldb::Env::Default()'
libbitcoin_server.a(txdb.o): In function `CLevelDBBatch':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::WriteBatch()'
libbitcoin_server.a(txdb.o): In function `Write':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:44: undefined reference to `leveldb::WriteBatch::Put(leveldb::Slice const&, leveldb::Slice const&)'
libbitcoin_server.a(txdb.o): In function `~CLevelDBBatch':
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
i:\code\bitcoin_git\bitcoin\src/leveldbwrapper.h:25: undefined reference to `leveldb::WriteBatch::~WriteBatch()'
...
...
...

I checked if libleveldb.a and libmemenv.a were available, and they were (located at .../src/leveldb).

Could anyone point me in the right direction?

I followed the instructions to the letter and I'm having this same problem when linking bitcoind.exe.  Does anyone know what I'm missing here?