16
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.
17
Keyhotee / Re: Keyhotee Status Update
« on: December 26, 2013, 04:31:35 pm »
I bid for 3 founder ids, eagerly waiting for the results 
18
General Discussion / Re: Announcing Angel Shares & BitShares Allocation
« on: December 26, 2013, 04:37:02 am »
bytemaster, how many confirmations does each transaction need to have before each day's deadline? People may choose to denote in the last minute.
19
General Discussion / Re: Announcing Angel Shares & BitShares Allocation
« on: December 26, 2013, 03:42:48 am »One quick question, does it matter if I donate from a multi-address PTS/BTC wallet? Or do I have to donate from a single address PTS/BTC wallet? I experienced MMC 2.0 that single address was easy. Please advise.
It should not matter, we will have tools to import all keys from your PTS and BTC wallets.
Thanks, I have given my donation. When will the AngelShares client available? Is there a due date for the donation?
AngelShares are non-transferrable, but will turn into something transferrable when we launch BitShares in Q1 2014. Everything received before the end of Jan 1, 2014 counts as part of the Jan 1, 2014 auction of 10000 AGS. Currently have have 5000 AGS as you are the first PTS bidder! After that every day is a fresh Auction. We wanted to give people some time to digest the system before the daily auctions start that way everyone has equal opportunity.
bytemaster, can you explain this:
Code: [Select]
Currently have have 5000 AGS as you are the first PTS bidder! Cause I've just donated BTC to the funding address.
20
BitShares PTS / Re: Couple of newbie questions.
« on: December 26, 2013, 01:56:30 am »
bytemaster, you said you've just launched AngelShares, where is the official announcement?
21
General Discussion / Re: Tx hijack to modify output
« on: December 26, 2013, 01:40:41 am »
toast, I read through the wiki and also peaked some code in the reference client implementation. It seems there is no tx integrity check at all, in other words, a miner seems able to modify tx's outputs. Merckle tree doesn't seem to prevent this from happening.
22
General Discussion / Re: Tx hijack to modify output
« on: December 25, 2013, 06:24:08 am »
Thank you, toast, I didn't know each tx has its own signature. is it part of the tx hash?
23
BitShares PTS / Re: Wallet got corrupted
« on: December 24, 2013, 09:41:41 am »xxd is just some command I guess, right?
@arubi, PM me your PTS address, I'll give you some PTS for helping me out here.
24
Keyhotee / Re: How will founder IDs be distributed?
« on: December 24, 2013, 09:39:00 am »
Good question. I bet for 3 ids already
25
General Discussion / Tx hijack to modify output
« on: December 24, 2013, 09:33:32 am »
I probably should have asked the question somewhere else, but I feel people here may also want to help me understand this little tech-detail.
I was wondering the whole afternoon today whether it's possible for a peer to change transaction outputs (so all money goes to a middleman address) before relaying the modified version of the transaction to the network? I don't see any mechanism to guarantee the integrity of transactions. This seems to be a problem especially when a client connects just to a couple of peers.
I was wondering the whole afternoon today whether it's possible for a peer to change transaction outputs (so all money goes to a middleman address) before relaying the modified version of the transaction to the network? I don't see any mechanism to guarantee the integrity of transactions. This seems to be a problem especially when a client connects just to a couple of peers.
26
BitShares PTS / Re: Wallet got corrupted
« on: December 22, 2013, 09:19:45 am »
OK, I think the pywallet script is still buggy, I'll spend sometime on it first.
27
BitShares PTS / Re: Wallet got corrupted
« on: December 21, 2013, 06:29:46 pm »
I'll give out 10% to people who helped recover my PTS
28
BitShares PTS / Re: Wallet got corrupted
« on: December 21, 2013, 06:28:44 pm »
I used this command to recover my lost pub/pri keys:
But I noticed all addresses start with "1" instead of "P" as seen in my protoshares client. Does anyone know how I can right this?
Code: [Select]
python ~/Desktop/pywallet/pywallet.py --recover --recov_device=tmp/wallet.1387632779.bak --recov_size 2Mo --recov_outputdir=. --otherversion=56
614 And I got output like this:Code: [Select]
Importing key 92/101:
Address (Bitcoin): 1FpiFBir5dWYPs8jgPWPQmL2buVVLpDH
Privkey (Bitcoin): 5KGKxM4w4SkM63YrFswNADT7bmvdf7JotG7sQ2NT2xygk1H
Hexprivkey: bed341dcfd51c3ab55eeece4ad681788b9e6ed276bbcea529e394a01c09909
Hash160: a297bd8b537dab2b82259c94b9f55e7a480260bc
Pubkey: 04cefe4dd00d2b10b5f879b41ec328ab8c3ff800d796d9ca6c9426b32853175ce8b0c835142778c72b2da1b1d6ad7b6fc91ff7d63f9d17ba5332eb66fbcbaed
Address (Bitcoin): 1P1Z999H9D5tqgdCEZ9Kwju9FE67yCZ
Privkey (Bitcoin): L3cefTdaMcCeVdfFaQfpxRnVxG8VHoCqbwFKSd4qwuYvUcX9F
Hexprivkey: bed341dcfd5123ab55eeece4ad681788a9e6ed276bbcea529e394a01c09909
Hash160: f16d98ae3eb037efc32eefcb4cb45f3a75db4f
Pubkey: 03cefe4dd0d2b1c0b5f879b41ec28ab80c3ff800d796d9ca6c9426b32853175c
But I noticed all addresses start with "1" instead of "P" as seen in my protoshares client. Does anyone know how I can right this?
29
BitShares PTS / Re: Wallet got corrupted
« on: December 21, 2013, 05:01:26 pm »
xxd is just some command I guess, right?
30
BitShares PTS / Re: Wallet got corrupted
« on: December 21, 2013, 04:28:53 pm »
I wonder what are the information inside those wallet.xxxxxx.bak files, if non of them can be parsed correctly, then they might just be different than the wallet files. What are these bak file designed for? There must be someway to use them...
