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

[simple-dice]

https://github.com/NM-Development/inputs.io-PHP-Wrapper/blob/master/Inputs.php

Wrote a basic PHP Wrapper for inputs.io's API.

The most basic functions like getting an account's balance, getting an account's transactions, sending a transaction, and getting a transaction's details.

I love your site, TradeFortress.  You should add more API functionality.

Also, could you look into allowing the API to send to an e-mail and address?

It's kind of silly IMO that you allow people to send to addresses but don't allow payments to be sent via inputs-inputs with the API...

Just change address= to recipient= and do a simple regex and then decide the process of sending.

Thanks and enjoy!

[1714842300]

1714842300

[1714842300]

1714842300

[1714842300]

1714842300

[1714842300]

1714842300

[1714842300]

1714842300

[🏰 TradeFortress 🏰]

It's kind of silly IMO that you allow people to send to addresses but don't allow payments to be sent via inputs-inputs with the API...

Just change address= to recipient= and do a simple regex and then decide the process of sending.

Thanks and enjoy!

Thanks! Address already supports email, Bitcoin addresses and usernames.

[simple-dice]

It's kind of silly IMO that you allow people to send to addresses but don't allow payments to be sent via inputs-inputs with the API...

Just change address= to recipient= and do a simple regex and then decide the process of sending.

Thanks and enjoy!

Thanks! Address already supports email, Bitcoin addresses and usernames.

Huh.. Odd.  It didn't send to an e-mail when I set address=email on the API.

I'll double-check my code.

[🏰 TradeFortress 🏰]

It's kind of silly IMO that you allow people to send to addresses but don't allow payments to be sent via inputs-inputs with the API...

Just change address= to recipient= and do a simple regex and then decide the process of sending.

Thanks and enjoy!

Thanks! Address already supports email, Bitcoin addresses and usernames.

Huh.. Odd.  It didn't send to an e-mail when I set address=email on the API.

I'll double-check my code.

Make sure you've encoded the @ sign.

[Mooshire]

I've got a suggestion for you TF: Vanity addresses
You can take advantage of piecewise generation to keep the shared wallet safe but still let users have vanity addresses.
For example:
1: The site provides the user with a user specific public key.
2: The user uses vanitygen or some other service to get a part private key for the address they want
3: The user imports the part private key into inputs.io, which combines the user-specific private key with the one the user provided to create the address.

Using this method, inputs.io is still the only handler of the site's private keys, but users can still use vanity addresses.
Since this might take some time to make and you'd probably only implement it if other people wanted it as well, i'd appreciate it if anyone reading this that thinks this is a good idea to state that here so TF knows that people want this. I believe I saw requests for vanity addresses before, but not piecewise support.
TF: Do you think this is a good idea?

[Mooshire]

Due to the way inputs.io work, if the user has the private key, he can fool it into crediting his coins, spend them, then transfer them back without using the site, i.e. spending them twice.
The vanity gen would have to be server side.

I don't think you understand piecewise generation. With piecewise generation, the user uploads a PART private key after generating an address using a public key given by the site. The site uses it's PART private key and combines it with the one the user gave it to create an actual bitcoin private key. The site is the only one with the full private key, so your argument is invalid  

EDIT: Just for clarity, the vanity gen would NOT run on the server, this would take much too many resources. The users would be supplying part private keys they made themselves or recieved from vanity address services.

[Mooshire]

I've got a suggestion for you TF: Vanity addresses
You can take advantage of piecewise generation to keep the shared wallet safe but still let users have vanity addresses.
For example:
1: The site provides the user with a user specific public key.
2: The user uses vanitygen or some other service to get a part private key for the address they want
3: The user imports the part private key into inputs.io, which combines the user-specific private key with the one the user provided to create the address.

Using this method, inputs.io is still the only handler of the site's private keys, but users can still use vanity addresses.
Since this might take some time to make and you'd probably only implement it if other people wanted it as well, i'd appreciate it if anyone reading this that thinks this is a good idea to state that here so TF knows that people want this. I believe I saw requests for vanity addresses before, but not piecewise support.
TF: Do you think this is a good idea?

Bumping this idea to last page

[🏰 TradeFortress 🏰]

It seems like the feature would have a very limited audience and would introduce significant complexity to the backend system. It's practical to allow users to generate vanity addresses up to three characters (case sensitive) or maybe 4 characters case insensitive, with the processing done on server. Would there be any interest in these vanity addresses?

[Mooshire]

It seems like the feature would have a very limited audience and would introduce significant complexity to the backend system. It's practical to allow users to generate vanity addresses up to three characters (case sensitive) or maybe 4 characters case insensitive, with the processing done on server. Would there be any interest in these vanity addresses?

I would be interested.

[Injust]

It seems like the feature would have a very limited audience and would introduce significant complexity to the backend system. It's practical to allow users to generate vanity addresses up to three characters (case sensitive) or maybe 4 characters case insensitive, with the processing done on server. Would there be any interest in these vanity addresses?

I would be interested.

There are already other free vamity address generators online, such as https://bitcoinvanity.appspot.com/.

[Mooshire]

It seems like the feature would have a very limited audience and would introduce significant complexity to the backend system. It's practical to allow users to generate vanity addresses up to three characters (case sensitive) or maybe 4 characters case insensitive, with the processing done on server. Would there be any interest in these vanity addresses?

I would be interested.

There are already other free vamity address generators online, such as https://bitcoinvanity.appspot.com/.

You don't understand, don't post things in topics when you don't know what is going on.
inputs.io is a shared wallet, so if I imported a vanity address, then coins that weren't mine would get sent to that address and I could take money that didn't belong to me.

[Injust]

It seems like the feature would have a very limited audience and would introduce significant complexity to the backend system. It's practical to allow users to generate vanity addresses up to three characters (case sensitive) or maybe 4 characters case insensitive, with the processing done on server. Would there be any interest in these vanity addresses?

I would be interested.

There are already other free vamity address generators online, such as https://bitcoinvanity.appspot.com/.

You don't understand, don't post things in topics when you don't know what is going on.
inputs.io is a shared wallet, so if I imported a vanity address, then coins that weren't mine would get sent to that address and I could take money that didn't belong to me.

Do not comprehend

[marketorder]

I sent you an email about the shopping cart app using  your API. Could you please respond to the app limitations you mentioned in the email I'd greatly appreciate it. My programmer asked about it

[marketorder]

Not at this time. I have developers testing the plugin. There's going to be a fee to download the app (extension) which will help fund future cost and upgrades. It's going to be compatible with WooCommerce, I will add additional shopping carts after I raised enough funds to cover the cost of further development.

The fee to download the plugin will be minimal compared to other premium extensions and plugins available for WooCommerce. We are testing the plugin now and should be available for download by this weekend or early next week. 

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

[marketorder]

TradeFortress will be able to test the application once completed if he chooses too. I'm paying programmers to test the application to make sure it works properly before I release it. It's a premium plugin  Inputs.io is not affiliated with me at this time. Just like anyone else out there can program an application or program using the API documentation that's why it's there to further the use and growth of the online wallet.

I don't want this to be a discussion about my plugin I was speaking to him privately about it but I was unable to get a response to a question my programmer asked.
'.

Not at this time.

This was addressed to inputs.io/TradeFortress.

[🏰 TradeFortress 🏰]

I don't want this to be a discussion about my plugin I was speaking to him privately about it but I was unable to get a response to a question my programmer asked.
'.

For reference this has been responded to.

[Mooshire]

I just sent in excess of 2.5 BTC with inputs and it sent it with 0 FEES

https://blockchain.info/tx/0d6f15e50201f8ffb02fc1872301948b82cf1c74bce7e6804e4d013f82de0d6e

Might want to not let it send without fees.

EDIT: Has confirmations now.

-----BEGIN BITCOIN SIGNED MESSAGE-----
Signed by Inputs.io on 02/10/13 05:56:09
The transaction 0d6f15e50201f8ffb02fc1872301948b82cf1c74bce7e6804e4d013f82de0d6e was sent by the owner of the address 17n1yi6T35snj6AKazc3VtTgmBJKukKFN. Messages signed from that address are representative of the actual sender of this transaction. This receipt was signed with one of the inputs of the transaction for verification.
-----BEGIN SIGNATURE-----
1HZpz62QnJCVv91yRzbUSBHVGxyy9GD6Me
H6x4BKD592YNKEC+3nqBVcN3buAiGvDdIo/y8BDge0wf8TS5EaKZCd3nKCqX1A+3I3cXTEoERWqYK2EbQ2eClo4=
-----END BITCOIN SIGNED MESSAGE-----

[🏰 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.

[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.

Thanks, good to see this.

[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.