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

marketorder

sr. member

Activity: 375

Merit: 250

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.

Quote from: ?? on ??

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

marketorder

sr. member

Activity: 375

Merit: 250

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

Injust

legendary

Activity: 1008

Merit: 1000

Quote from: Mooshire on September 30, 2013, 10:27:43 PM

Quote from: Injust on September 30, 2013, 10:04:57 PM

Quote from: Mooshire on September 30, 2013, 09:27:06 PM

Quote from: 🏰 TradeFortress 🏰 on September 30, 2013, 08:20:29 PM

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 Tongue

Mooshire

sr. member

Activity: 322

Merit: 250

Quote from: Injust on September 30, 2013, 10:04:57 PM

Quote from: Mooshire on September 30, 2013, 09:27:06 PM

Quote from: 🏰 TradeFortress 🏰 on September 30, 2013, 08:20:29 PM

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

legendary

Activity: 1008

Merit: 1000

Quote from: Mooshire on September 30, 2013, 09:27:06 PM

Quote from: 🏰 TradeFortress 🏰 on September 30, 2013, 08:20:29 PM

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

sr. member

Activity: 322

Merit: 250

Quote from: 🏰 TradeFortress 🏰 on September 30, 2013, 08:20:29 PM

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.

🏰 TradeFortress 🏰

vip

Activity: 1316

Merit: 1043

👻

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

sr. member

Activity: 322

Merit: 250

Quote from: Mooshire on September 29, 2013, 01:09:13 PM

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

Mooshire

sr. member

Activity: 322

Merit: 250

Quote from: ?? on ??

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 Cool

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

sr. member

Activity: 322

Merit: 250

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?

🏰 TradeFortress 🏰

vip

Activity: 1316

Merit: 1043

👻

Quote from: simple-dice on September 28, 2013, 09:55:26 PM

Quote from: 🏰 TradeFortress 🏰 on September 28, 2013, 08:36:35 PM

Quote from: simple-dice on September 28, 2013, 04:11:40 AM

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.

simple-dice

newbie

Activity: 59

Merit: 0

Quote from: 🏰 TradeFortress 🏰 on September 28, 2013, 08:36:35 PM

Quote from: simple-dice on September 28, 2013, 04:11:40 AM

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 🏰

vip

Activity: 1316

Merit: 1043

👻

Quote from: simple-dice on September 28, 2013, 04:11:40 AM

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

newbie

Activity: 59

Merit: 0

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!

🏰 TradeFortress 🏰

vip

Activity: 1316

Merit: 1043

👻

Done. Your address will only show up if you don't have a callback set to prevent issues with users sending to a BTC address when they want to send to a merchant.

Mooshire

sr. member

Activity: 322

Merit: 250

Quote from: 🏰 TradeFortress 🏰 on August 08, 2013, 07:19:38 PM

As you may have heard, Lavabit has shut down. Here is the a quote from their website:

Quote

My Fellow Users,

I have been forced to make a difficult decision: to become complicit in crimes against the American people or walk away from nearly ten years of hard work by shutting down Lavabit. After significant soul searching, I have decided to suspend operations. I wish that I could legally share with you the events that led to my decision. I cannot. I feel you deserve to know what’s going on--the first amendment is supposed to guarantee me the freedom to speak out in situations like this. Unfortunately, Congress has passed laws that say otherwise. As things currently stand, I cannot share my experiences over the last six weeks, even though I have twice made the appropriate requests.

If you have a @lavabit (or @tormail) email, please create a new account with another email and contact us at [email protected]

-----

You can now see the historical "value at time of transaction" or "value when sent" in fiat. We are storing the BTCUSD, BTCEUR, BTCCAD and BTCGBP conversion rates. If you're a developer, you can access this data too - see advanced in the API page.

Please note that only recent transactions has this value as we only recently started storing exchange data. As outlined in our legal disclaimer, exchange rates are for informational purposes only and we do not guarantee the accuracy.

----

Quote

Here's an idea
Say I want to get some to pay me, but I'm logged out of ky wallet and cant copy paste my address or otherwise do not have access to it and I want to give my inputs account to someone to pay me. how about instead of 1v.io/Mooshire redirecting to whatever it gives them an address that they fan send to, the default receive address of that wallet so that they can still send me coins. Feedback?

Implemented. Thanks for the feedback!

----

Also, welcome to new members to the Inputs family: BitAds.net and 3-6dice.com

Can you consider making the shortlinks redirect to an actual address like I suggested a while ago and you said you did? This is of course only if they're not logged in. There is literally no point to using one of these shortlinks because it's easier to give someone your username. But if they worked for both logged in and non-members than there would be an actual reason to use them.

wuala

full member

Activity: 163

Merit: 100