|
Totally agree.. While I have not had any bad experience with MTGOX, the P2P at BitFloor is very appealing and I have already begun to work my future trades through them because of this.
Stay on top of things or get left behind.
|
|
|
|
The patent is already shown to not be valid in this case ... and even if for some stupid reason some typically zero intelligence judge did say the patent covers this, well it expires this year anyway from what I've read.
That's great news! Even so, this will prove to be a very enlightening and educational experience for me as I've wanted to help maintain other packages too. This ECDSA thing has motivate me to finally learn how this stuff works. |
|
|
|
excellent work! I had a discussion with a guy in #Fedora-dev who helped me out and gave me nearly the same instructions. I have been planning on giving it a go, but it's just been too busy. Here's the overview of the discussion we had. We should compare notes and take it to the end - through setting up a repo. I may have some time to work on this today. <wolfy> it's almost 3 AM over here so I will not be staying much longer
<wolfy> so let me tell you the basic stept
<wolfy> steps
<wolfy> 1. yum install fedora-packager
<wolfy> 2. decide what user you will use to build packages as. I use my normal user account
<wolfy> do not ever build as root
<wolfy> install mock
<wolfy> become the user you want to build as ( su - THATUSER)
<wolfy> run rpmdev-setuptree
<wolfy> download the openssl.src.rpm from fedora
<wolfy> rpm -i openssl.src.rpm ( this step will explode the src and allow you to later edit the spec )
<wolfy> download the original source
<wolfy> edit ~/rpmbuild/SPECS/openssl.spec
<wolfy> replace the file name in SOURCE0 with the name of the downloaded original
<wolfy> add a line in front of the %changelog section , using the same format as the existing ones
<wolfy> and put in there the new version and the comments that you seem fit for the changelog
<wolfy> ah, also, do not forget to edit the version and release fields from the top of the spec file, make them coincide with the name of the new source
<wolfy> save the spec file
<wolfy> run rpmbuild -bs ~/rpmbuild/SPECS/openssl.spec
<wolfy> this will create a new src.rpm
<wolfy> let's say it's called ~/rpmbuild/SRPMS/newopenssl.src.rpm
<wolfy> run mock -r fedora-16-x86_64 ~/rpmbuild/SRPMS/newopenssl.src.rpm
<wolfy> and come back to me with the issues that you face
<wolfy> ah
<wolfy> one more thing
<wolfy> you need to add the user that you will use to build to the group mock
<wolfy> after installing mock
<wolfy> otherwise mock will refuse to run
Ultimately I plan on hosting an openssl repository 'with signatures n shit' to make it even easier for people to use EC on Fedora. |
|
|
|
|
Michael, I agree with most of your sentiments... but...
Most of these Bitcoin projects are not funded by anyone, nor is there necessarily a profit model for any of it. Unless everyone agreed to pay a local penny (or so, at the current exchange rate, in bitcoin) to the client author (Hey, Thomas, that's an idea I can get behind, have you thought about this?).
But until then, it is not likely that the guy writing all this bad ass code is going to be able to also fully document it - himself or pay someone to do it.
I suggest one of the following for you and everyone else that wants to see more work on this client:
option 1) tip the developer everytime a useful release comes out. It gives him a great pat on the back and motivates him to continue. The funds might go to paying someone to maintain the documenation site.
option 2) offer to help them out. When you do figure out how something works and documentation is deficient, write it up and email it to him. at least then all he has to do it cut and paster.
One of those should apply to everyone that enjoys this simply bad ass client.
|
|
|
|
To everyone that chipped in... here's your reward... Thank you for fighting against stupid ass corrupt local government!!! https://i.imgur.com/eSSLt.jpg |
|
|
|
|
Fixed. I like these new features.. one more to think about, could a receiving address be specified as a change address? I'd like to always spend money from a vanity address without having to constantly refund it after every spend. It seems like a neat way to let people know I'm the one tipping them (if they recognize they vanity).
(BTW, some bitcoins on their way to your server address)
|
|
|
|
|
Import worked perfect with a different format.
Now I'm noticing that the calculated fee is not populating the fee box even though there is a .001 per input specified in the client settings.
I priorities my new vanity key, manually entered in a fee, hit send, and now I'm getting 'global name 'prioritized_addresses' is not defined'.
|
|
|
|
can you check if the imported address is in your wallet file?
2012-06-06:0932 PDT
[tux@powerball extract]$ electrum import 1TUx7o2FKVfhjko3gNmB3zwVuNdxfHcer:HiE5XJ<redacted>
keypair imported
2012-06-06:0932 PDT
[tux@powerball extract]$ grep -i --color 1tux ~/.electrum/electrum.dat
grep not finding it. One thing I did notice is that beginning of the private key didn't start with a 5 which I'm kinda use to seeing. I left a little bit of the private key in the example above. Dunno if that has anything to do with the problem. |
|
|
|
does it show up in text mode?
Not at all. 2012-06-06:0838 PDT
[tux@powerball extract]$ electrum import 1TUx7o2FKVfhjko3gNmB3zwVuNdxfHcer:<redacted>
keypair imported
2012-06-06:0840 PDT
[tux@powerball extract]$ electrum addresses
14Jsnz5PcGGMKNep8SbMjRTYd9NWnBSaMW 1
1CHuQNXk34fGrpyU9qBqJwKgPxUHpcU5q7 2
1Ai87sV3AMNX7JoWukXg8TfQPMWdcs5Dj4 3
1JNZGwAjMRrmrqMYKWFH9oJth8cvzUJman 4
12ckR9ysupmMRqimPEL421nUmg1y5Q1eUK 5
2012-06-06:0840 PDT
[tux@powerball extract]$ electrum addresses -ak
14Jsnz5PcGGMKNep8SbMjRTYd9NWnBSaMW:<redacted> 1
1CHuQNXk34fGrpyU9qBqJwKgPxUHpcU5q7:<redacted> 2
1Ai87sV3AMNX7JoWukXg8TfQPMWdcs5Dj4:<redacted> 3
1JNZGwAjMRrmrqMYKWFH9oJth8cvzUJman:<redacted> 4
12ckR9ysupmMRqimPEL421nUmg1y5Q1eUK:<redacted> 5
16AdUzurZ3zD68ebe8a57BViDWeU1nftDj:<redacted> [change] 1
edit: this makes me think that imported addresses should have a coor too
That would be awesome!
|
|
|
|
|
Trying .54...
I imported a vanity key and it does not show up in the receive list. I'd like to set this as a priority address but can't since it's not there.
What exactly does a frozen address do (or not do)?
Also, I can't remember if I asked for this or not, but would it be possible to sort the lists by clicking on column headers?
|
|
|
|
|
Why aren't we using a freenode web chat room?
Wouldnt that be better? the chat log could be posted here afterward.
|
|
|
|
|
BTW,
THANK YOU PHRAUST for the cool logo. If you guys need any artwork, please give phraust in IRC a holla.
|
|
|
|
Due to a domain collision with BitcoinWeekly.com, I've officially rebranded the BitcoinWeekly.info website to "Bitcoin Informant". The weekly newsletter will now be published under this new domain BitcoinInformant.com Below is a sample of the newsletter in the new format. Current translations: Brazilian Portuguese, Czech, English with Vietnamese, Russian, Ukrainian coming soon. If you would like to help out with a translation in your language, I am offering to place your tipping address on the newsletter so you can receive some incentive to help out. Also, we just got our 20th subscriber. A raffle was drawn and Miguel Pacheco of Texas won the first free tshirt giveaway. I'd do another raffle when we get 40 subscribers.  |
|
|
|
|
We were suppose to hook up at one point. I guess we both got busy and forgot. I'll try again.
|
|
|
|
|
Show Posts
