Inputs.io | Instant Payments, Offchain API, Secure Wallet, 235k+ BTC transferred

[Mooshire]

You can now generate addresses with a custom prefix, commonly referred to as "vanity addresses". Think of license plates that spell out a world, prefixes are a similar concept - such as 1BobLKNvSz7333peq3ymJzLmaV6jg7gPnt.

Bitcoin addresses have certain limitations - such as lowercase L (l), uppercase i (I) and uppercase o (O) cannot be used. In addition, you can generate vanity addresses up to 4 characters long with Inputs (eg 1Love). Please note that it may take up to one minute to generate a vanity address.

Why not allow people to pay for longer addresses than 4 characters long? Would earn more money, and help people to easily get and implement vanity addresses.

This might work but wouldn't that put a much heavier load on the server?

[🏰 TradeFortress 🏰]

You can now generate addresses with a custom prefix, commonly referred to as "vanity addresses". Think of license plates that spell out a world, prefixes are a similar concept - such as 1BobLKNvSz7333peq3ymJzLmaV6jg7gPnt.

Bitcoin addresses have certain limitations - such as lowercase L (l), uppercase i (I) and uppercase o (O) cannot be used. In addition, you can generate vanity addresses up to 4 characters long with Inputs (eg 1Love). Please note that it may take up to one minute to generate a vanity address.

Why not allow people to pay for longer addresses than 4 characters long? Would earn more money, and help people to easily get and implement vanity addresses.

It is unlikely the use will justify the implementation cost. For now, support@inputs.io will happily help you with reasonable vanity addresses for free.

[Boelens]

You can now generate addresses with a custom prefix, commonly referred to as "vanity addresses". Think of license plates that spell out a world, prefixes are a similar concept - such as 1BobLKNvSz7333peq3ymJzLmaV6jg7gPnt.

Bitcoin addresses have certain limitations - such as lowercase L (l), uppercase i (I) and uppercase o (O) cannot be used. In addition, you can generate vanity addresses up to 4 characters long with Inputs (eg 1Love). Please note that it may take up to one minute to generate a vanity address.

Why not allow people to pay for longer addresses than 4 characters long? Would earn more money, and help people to easily get and implement vanity addresses.

It is unlikely the use will justify the implementation cost. For now, support@inputs.io will happily help you with reasonable vanity addresses for free.

Ah, alright. I generate my own but I understand why people would want it. Is it possible to import private keys into Inputs? Like, generate in example 1yoloswag and import this privatekey (once generated) into inputs, and then use that address on inputs.io? Also, question apart from inputs.io, I just realized, if I were to generate 1BoeLens (like I have), it'll have some random things after it like ATmad51 etc. However, what happens if someone were to generate the exact same address? I'm no math experts but I think the odds would be astronomically small, but couldn't you "brute force" addresses like that? Especially tiny ones.

[Eternity]

Have been using this from such a long time

Truly amazing

[Mooshire]

You can now generate addresses with a custom prefix, commonly referred to as "vanity addresses". Think of license plates that spell out a world, prefixes are a similar concept - such as 1BobLKNvSz7333peq3ymJzLmaV6jg7gPnt.

Bitcoin addresses have certain limitations - such as lowercase L (l), uppercase i (I) and uppercase o (O) cannot be used. In addition, you can generate vanity addresses up to 4 characters long with Inputs (eg 1Love). Please note that it may take up to one minute to generate a vanity address.

Why not allow people to pay for longer addresses than 4 characters long? Would earn more money, and help people to easily get and implement vanity addresses.

It is unlikely the use will justify the implementation cost. For now, support@inputs.io will happily help you with reasonable vanity addresses for free.

Ah, alright. I generate my own but I understand why people would want it. Is it possible to import private keys into Inputs? Like, generate in example 1yoloswag and import this privatekey (once generated) into inputs, and then use that address on inputs.io? Also, question apart from inputs.io, I just realized, if I were to generate 1BoeLens (like I have), it'll have some random things after it like ATmad51 etc. However, what happens if someone were to generate the exact same address? I'm no math experts but I think the odds would be astronomically small, but couldn't you "brute force" addresses like that? Especially tiny ones.

It's a shared wallet, this would compromise the wallet, so it will never be added.

[🏰 TradeFortress 🏰]

Ah, alright. I generate my own but I understand why people would want it. Is it possible to import private keys into Inputs? Like, generate in example 1yoloswag and import this privatekey (once generated) into inputs, and then use that address on inputs.io? Also, question apart from inputs.io, I just realized, if I were to generate 1BoeLens (like I have), it'll have some random things after it like ATmad51 etc. However, what happens if someone were to generate the exact same address? I'm no math experts but I think the odds would be astronomically small, but couldn't you "brute force" addresses like that? Especially tiny ones.

Importing private keys can't be implemented.

It is possible however as the odds are astronomically small, making it irrelevant. Bitcoin uses secp256k1, and private keys are 256 bits, or 1.1579209e+77.

[b!z]

You can now generate addresses with a custom prefix, commonly referred to as "vanity addresses". Think of license plates that spell out a world, prefixes are a similar concept - such as 1BobLKNvSz7333peq3ymJzLmaV6jg7gPnt.

Bitcoin addresses have certain limitations - such as lowercase L (l), uppercase i (I) and uppercase o (O) cannot be used. In addition, you can generate vanity addresses up to 4 characters long with Inputs (eg 1Love). Please note that it may take up to one minute to generate a vanity address.

Why not allow people to pay for longer addresses than 4 characters long? Would earn more money, and help people to easily get and implement vanity addresses.

It is unlikely the use will justify the implementation cost. For now, support@inputs.io will happily help you with reasonable vanity addresses for free.

Ah, alright. I generate my own but I understand why people would want it. Is it possible to import private keys into Inputs? Like, generate in example 1yoloswag and import this privatekey (once generated) into inputs, and then use that address on inputs.io? Also, question apart from inputs.io, I just realized, if I were to generate 1BoeLens (like I have), it'll have some random things after it like ATmad51 etc. However, what happens if someone were to generate the exact same address? I'm no math experts but I think the odds would be astronomically small, but couldn't you "brute force" addresses like that? Especially tiny ones.

Read this thread: https://bitcointalk.org/index.php?topic=296141.0

It should give you an idea of how it is nearly impossible.

[termhn]

Made myself an account. No complaints so far, GREAT online wallet service!

[rme]

Please enable HSTS to avoid sslstrip or a MITM replacing the http page.
https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

With PHP check if the page is been served in HTTP, if so redirect to HTTPS.
In HTTPS set the HSTS header:

Code:

header("strict-transport-security: max-age=31536000");

That tells the browser to only use the HTTPS versión of inputs.io for a year (31536000 seconds).
So, my browser will go directly to https even if I have no internet conection.

[🏰 TradeFortress 🏰]

Please enable HSTS to avoid sslstrip or a MITM replacing the http page.
https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

With PHP check if the page is been served in HTTP, if so redirect to HTTPS.
In HTTPS set the HSTS header:

Code:

header("strict-transport-security: max-age=31536000");

That tells the browser to only use the HTTPS versión of inputs.io for a year (31536000 seconds).
So, my browser will go directly to https even if I have no internet conection.

Done. Thank you.

[🏰 TradeFortress 🏰]

Bump

[🏰 TradeFortress 🏰]

Counter-bump:

As a developer:
Are there plans for a test version? Ideally connected to testnet.

The internal testing / development environment runs on testnet, but a publicly I think there's little point when you can make 0.0001 transactions for the purpose of testing.

[Mooshire]

Counter-bump:

As a developer:
Are there plans for a test version? Ideally connected to testnet.

The internal testing / development environment runs on testnet, but a publicly I think there's little point when you can make 0.0001 transactions for the purpose of testing.

It might be easier on a devs mind when they know the only coins that could be stolen with their API key is test net coins.

[🏰 TradeFortress 🏰]

Home page redesign coming soon!

[cozie]

hi, i try to login in my account and in Overview page all say "LOADING" and actually never load anything, bitcoin address not show up, and i can't change page
anybody else have the same issue?

[🏰 TradeFortress 🏰]

hi, i try to login in my account and in Overview page all say "LOADING" and actually never load anything, bitcoin address not show up, and i can't change page
anybody else have the same issue?

What browser are you on? Have you tried to do a hard refresh / cache clean? If that doesn't help, contact support@inputs.io

[cozie]

i try with firefox 24.0 and chrome 30.0.1599.101
is strange because i use it around 7-8 hours ago and was working so should be no problem on my side

[edit]
i use another internet connection and it works, then come back to my usual internet connection and work again
[/edit]

[ninjaboon]

Home page redesign coming soon!

can't wait. the current one is already good.

[🏰 TradeFortress 🏰]

Take a look at the new Inputs.io homepage.

[celebindo]

Hi can you please provide me with a refund for the BFL miner I ordered a month ago?