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 - arcke

Pages: 1 2 3 4 5 [6] 7 8
76
Marketplace / Re: 100 PTS - BOUNTY - Import wallet.dat Private Keys via API call (2 PTS Referral)
« on: December 31, 2013, 03:36:41 pm »
Quote from: toast on December 31, 2013, 05:42:55 am
Yep of course, the idea was to just get it to work *at all* and the prune
If someone comes across specifications for bitcoin/protoshares wallet.dat-files this can help big time. Right now we have been using bitcoin and protoshares as reference implementations for importing wallets.

77
Marketplace / Re: 1200 PTS - New Invictus Website Ready to Deploy [ACTIVE]
« on: December 31, 2013, 02:29:51 am »
I am going to write a protoshares summary. Let me know what you think is important about protoshares that should be in the summary or any thoughts that might lead us to write a catching summary. I will think about this myself and greatly appreciate your input.

Also, I think images about protoshares, graphical depictions explaining some technicalities, or other artwork will greatly enhance the pleasure of consuming a summary. This also holds true for all the other summaries.

78
Marketplace / Re: 100 PTS - BOUNTY - Import wallet.dat Private Keys via API call (2 PTS Referral)
« on: December 30, 2013, 11:52:03 pm »
I have some code for reading the wallet. How do I execute the unit tests or a specific unit test?

Edit: Nevermind, I just run them directly.

Edit2: Working with code from https://github.com/bitcoin/bitcoin/blob/master/src/rpcdump.cpp#L131

79
Keyhotee / Re: Screen Shot
« on: December 30, 2013, 04:23:06 pm »
About the year of birth input field. Personally I prefer to see the full year when I am entering this information, so instead of 65, I could choose 1965. Does anyone disagree? It would just have "smoothened" my first Keyhotee GUI impression, so I am bringing it up.

80
General Discussion / Re: Invictus Innovations - Help Wanted!
« on: December 30, 2013, 03:29:10 pm »
Quote from: pvaladares on December 30, 2013, 12:53:03 pm
Is there any guide to build under Ubuntu? I get various compilation errors.
https://bitsharestalk.org/index.php?topic=1672.msg19078#msg19078

What are you doing now to build it and what errors are you getting? Let me know where you get stuck.

81
Marketplace / Re: 100 PTS - BOUNTY - Import wallet.dat Private Keys via API call (2 PTS Referral)
« on: December 30, 2013, 05:50:57 am »
Quote from: toast on December 30, 2013, 05:42:07 am
Yeah, I've looked through the code and it shouldn't be too hard, I think once I actually start working I'll be able to finish in less than a day. arcke, want to split the work somehow?

Right now I'm almost done getting this to build, successfully got it to use g++ for CXX objects but still working on getting it to use gcc instead of clang for C objects. Very good learning experience. Turns out OSX mavericks quitely links g++/gcc to clang, how nice
Yes, when I find an opportunity to split work I will let you know. For now I am still just investigating.

First method of interest I found is CWallet::Unlock. Reverse engineering this will tell us how we can decrypt an encrypted wallet with a passphrase. To be done: investigate if we can reuse code from bitcoin/protoshares to do this.

I am working on Linux, cant help you with the OSX build specifics.

82
Marketplace / Re: 100 PTS - BOUNTY - Import wallet.dat Private Keys via API call (2 PTS Referral)
« on: December 30, 2013, 05:27:19 am »
This means we can reuse code from bitcoin. I have been looking at bitcoin/src/wallet.{h,cpp}. I might be able to do this basing my solution on bitcoin code. For now we should make unit tests firsts and put them online.

83
Marketplace / Re: 100 PTS - BOUNTY - Import wallet.dat Private Keys via API call (2 PTS Referral)
« on: December 30, 2013, 05:14:18 am »
Quote
To be accepted, a unit test case must be provided using boost unit tests that verifies that the keys can be imported and converted to the proper PTS address.
I am in doubt regarding the task demanded by the bounty. What types of wallets should the method import? Should it import protoshares wallets into bitshares or is this method universally importing wallets of all bitcoin-forks or just bitcoin?

84
General Discussion / Re: Ethereum: The Ultimate Smart Contract and Decentralized Application Platform
« on: December 30, 2013, 02:27:59 am »
Quote from: toast on December 29, 2013, 06:50:57 pm
IMO this sort of project should NOT be using a turing-complete language as the foundation. Bitcoin's scripting language was designed to be not turing-complete for a reason. We want our protocol language to be good for correctness proofs, not malware.
What was the reason? Reasons I can imagine are simplicity and efficient encoding or speed. Are there security considerations?

I imagine a protocol in a high-level language could be compiled to ethereums script language. This would still allow for languages which are more suitable for correctness proofs.

85
General Discussion / Re: Transition from PTS to Bitshares
« on: December 29, 2013, 07:03:40 pm »
Quote from: HCarvalho on December 29, 2013, 06:27:04 pm
where do we do that?
BitShares is currently still under development. You can track development and check out the code on github.

BitShares
Invictus

86
Keyhotee / Re: compile keyhotee on ubuntu 13.10
« on: December 28, 2013, 04:04:01 pm »
What procedure are you using to get the source and compile? What version of qt is installed? I am using http://download.qt-project.org/official_releases/qt/5.2/5.2.0/qt-linux-opensource-5.2.0-x86_64-offline.run.

First, check if you have all dependencies then

cd <where you want the source to be>
git clone https://github.com/InvictusInnovations/keyhotee
cd keyhotee
git clone https://github.com/InvictusInnovations/BitShares
cd BitShares
git clone https://github.com/InvictusInnovations/fc
cd ..
cmake . (or QTDIR=<where your qt is> cmake .)
make

Now 'bin/Keyhotee ' starts keyhotee.

87
MemoryCoin / Re: [ANN] New Pool for MMC
« on: December 28, 2013, 12:23:49 am »
Where can we find individual user statistics?

88
MemoryCoin / Re: [ANN] [BETA] Extasie MMC Pool!
« on: December 28, 2013, 12:10:53 am »
I get these every time I run cpuminer

[2013-12-28 01:09:51] thread 3: 4 hashes, 1.97 khash/s
[2013-12-28 01:10:07] JSON-RPC call failed: {
   "message": "upstream RPC error",
   "code": -4
}
[2013-12-28 01:10:07] submit_upstream_work json_rpc_call failed
[2013-12-28 01:10:07] ...retry after 30 seconds

89
MemoryCoin / Re: One pool with almost 100% hashpower
« on: December 26, 2013, 07:16:53 pm »
A lesson to be learned, being memory-hard is not the only thing keeping a few from getting the most of out of coin mining.

90
MemoryCoin / Re: One pool with almost 100% hashpower
« on: December 26, 2013, 04:41:17 pm »
Quote from: reorder on December 26, 2013, 04:32:22 pm
Quote from: isaacgoldbourne on December 26, 2013, 04:29:06 pm
Quote from: reorder on December 26, 2013, 04:25:58 pm
Quote from: isaacgoldbourne on December 26, 2013, 04:05:27 pm
Quote from: lest on December 26, 2013, 04:01:33 pm
Currently there is one pool with almost 100% hashpower. It makes MemoryCoin very unsecure at the moment.

We definitely should do something with it.
The creator has sold the source code to "a few" people.

Personally I feel it should be opensourced.

Still got a few days until they create pools :S has the damage already been done?
I am asking how much it will cost to buy, but I imagine it is a ridiculous sum. I would have a pool up by this evening however.

Opesourced to community of greedy, selfish miners who don't mind to mine with every bit of cpu power they can get for free or steal? Hmm, what could possibly be wrong with this?
The fact that they are already doing this, but on a pool that can damage the network
Not this early. You do not want to 51% the coin you have income in, that would kill it right away.
In some scenarios this might actually be the motive. Imagine traditional government systems trying to cripple new cryptocurrencies by 51%-ing them.

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

Page created in 0.197 seconds with 23 queries.