You want to choose 32 characters?
No. I want any address that is 32 characters long. According to the Bitcoin wiki, Base58 can be as short as 27 characters. |
|
|
|
|
How can I get vanitygen to generate an address with a certain amount of characters - for example 32 or 33?
|
|
|
|
|
Yes, but you'll need more than 100 posts to get paid.
Also, please leave me a trust feedback!
|
|
|
|
Making a transaction now has a cool progress bar thanks to NProgress  |
|
|
|
Total speculation here but I do recall FC mentioning that he was addressing the orphan block / no transaction fees issue. It may be that a portion of his hash is aimed at BTCguild or something. He has done so in the past and we might not see it until the coins move on divday.
We'd see the userid on BTCGuild then. |
|
|
|
I've heard nothing but good things about https://www.privateinternetaccess.com. Costs $35 per year and they accept bitcoin. I don't use them personally, but I plan on switching to them when my current VPN expires No, no, just no. If you use a US based VPN after what Lavabit's founder said you're a dumbass. |
|
|
|
On certain environments (like Chrome/Firefox with no hardware RNG access through JS), Blockchain.info is susceptible to the same attack (reused R value) outside of Android. See this thread for more information: https://bitcointalk.org/index.php?topic=277595.0 |
|
|
|
Thanks for the 0.24, TradeFortress. I would like to participate again and receive payment to the inputs.io wallet linked in my sig. PLease confirm if i am entered correctly, thanks.
Confirmed. |
|
|
|
Let's see if I understand this completely:
So.. I should make an function that can repeat the results based on the input?
I first show the user our server seed hash, then I let the user generate an user seed (or set it for them generate the user seed on the client with Javascript).
For the roll I use the server seed (not the hash) and the user seed and the number of the bet since using this server seed. After the rolls I show the server seed and give them a functionality to input that server seed and user seed and roll number to verify the result again.
The user can verify the server seed by hashing it himself, since the chance of duplicate hashes is basicly zero
To make it uncheatable I generate a new server seed whenever the user wants to see the original seed (or change it once a day like said in the first post).
Sounds good |
|
|
|
Inputs.io support  (it's perfect for small amounts and when you want instant transactions) I actually was using Inputs originally, but I ended up using coinbase API because I found a way to make it fill in the parameters for each post automatically. What do you mean? You can do that too with Inputs - the notes / message field. |
|
|
|
I also recommend to not go with major design overhauls to make it look web 2.0. I use Bootstrap a lot, but it's simply not what will work with the Bitcoin community. That means, don't start your project off with Bootstrap's large empty spacing, font size, large buttons, white/grey/black palette. Making something more web 2.0 has disastrous results for a technical internet community. DigitalPoint migrated to the latest version of vBulletin which is like the direction your UI is going. Take a look at how they are doing:  You can quite easily see that after upgrading their forum to be more web 2.0 / shiny, their userbase stopped visiting as much. They had to move to another forum software that was more traditional, and better for "power users". --- It should also be noted that Google will penalize you if you serve a different version to GoogleBot. See this video: http://searchengineland.com/library/search-engine-optimization/seo-cloaking-doorway-pagesYour crawler interface will get your forum software significantly penalized - Google cares if you serve it a substantially different HTML, it can't detect if what you are doing is "reducing bandwidth" or whatever - if a diff is significant, you get slapped with a hefty penalty. |
|
|
|
Not exactly a fan of the mock up UI.  Individual posts take up too much space, and black on grey is not a good color combination for long reads. The <h2> or whatever makes the subject take up disproportionally more space - even through in 99.5% of the posts the subject of replies convey no additional information. The topic list UI is not well designed. The user bar should have a constant width that makes it easier to skim through the subjects. There's too much clutter to the right that makes it hard to see replies / views at a glance, and there is no last reply message. The timestamp is also unfriendly - you should use relative time (eg 3 minutes ago, not dates unless it is very old). Most people also generally read from left to right. IMO the sidebar would be better positioned on the left (and you should really get another default color palette). The default theme should be minimalistic like the current theme. Nothing that looks "web 2.0": no speech bubbles, no significant space between posts, no significant hover effects, and few rounded corners.
The default theme must work well with all functionality and a reasonable page layout on text browsers without JavaScript. It should also work perfectly on browsers with unusually small browser dimensions. It should be at least somewhat usable (though maybe not pretty) on ancient and broken browsers like IE6.
Same color scheme as we have now: light with some blue. Keep in mind that the audience here is much more technical, and are more power users. In addition, a much more significant amount of users runs with JS disabled or NoScript for security reasons (against code injection, using tor, whatever), your user interface should be virtually identical (like right now) for users without JS enabled. This reminds me of the disastrous Google Reader redesign - too much empty space, too much user friendlyless at the sacrifice of user functionality - or digitalpoint (that's a way better example). Many users (especially power users) do not have an avatar here. How will that be presented? |
|
|
|
Choose another game behavior. Heads and tails has 50% probability and zero house edge. The main benefit of proven fair feature is to prove that house doesn't craft random items during game, but picks really random ones. So in your case it would be "Provably cheat" game  Well let's change scenario: If you click play you have an 49.5% of doubling your money. How can I prove it now? You need to use hashing and server / client seeds to determine the result. Basically: both the server and player must be able to modify the result in an unpredictable way. |
|
|
|
Inputs.io support (it's perfect for small amounts and when you want instant transactions) |
|
|
|
* Website Changes
IANAL but the wordings would probably not hold up in court making it a moot point.
Please see SEC v. SG, Ltd., 265 F.3d 42, particularly about how SEC did not challenge the virtual securities but only the specially noted "privileged company" which was noted as a security. * Inverted yield curve
An inverted yield curve tends to exacerbate maturity mismatch which in turn increases vulnerability to bank runs. On the other hand, CoinLenders builds up more trust the longer we operate, and we can offer fee rebates to compensate for that. The relation to Inputs.io has not been clear. Inputs.io advertises a shared wallet as a feature (which is undoubtedly is) but makes insight into individual wallets difficult and also opens up the possibility of re-hypothecation. CoinLenders uses Inputs.io for Bitcoin payment processing. CL and Inputs' books are completely separate, as it should be. If CL makes a significant portion of uncollateralized private loans, this may expose CL to an increased default risk. CoinLenders does not invest a significant amount into collateralize private loans. Most of our loans are fully secured. Little or no insight to balance sheet. Primarily capital ratio. CL intentionally has no balance sheet to maintain a competitive advantage. You can see transparent reports every two weeks for BTCINVEST however. |
|
|
|
It should be possible to check the 301 redirects (on the server) and then base a blacklist off that. |
|
|
|
|
1.5 BTC for whole project.
|
|
|
|
reporting. 1A1XXJms4Zy1fvWVuprXGqGfYk18DyCviv Paid up to here |
|
|
|
|
Show Posts
