Database with 1500+ stores/services that accept BTC as payment.
Description: A database with more than 1500 stores and services that accept Bitcoin as payment method.
Starting bid: 0.5 BTC
Buy it now: 3 BTC
End date and time: January 02, 2014
Payment methods accepted: Bitcoin and Litecoin.
Additional information: The data are stored in JSON files and already have a structure, but I can provide a database script (.sql, for e.g) and change the structure following the buyer needs (and following my limitations as programmer).
Currently, the data are disposed in a lot of JSON files that can be easily parsed. When I say "store", I want mean "store / service" (goods / services), remember. This is the currently data structure:
- Name: The name of store / service
- Description: Description of store. Every store have, at minimum, a little description. Some stores have telephone, address and e-mail address too.
- Url: The url for the site of this store.
- Type: The type of this store. (can be "Goods" or "Services").
- Category: The category that this store belongs to. I have added a lot of categories, can't list all (every 'type' have their owns 'categories')
The JSON files are disposed like that:
|-- data/
|-- goods/
|-- <category1-name>-data.json
|-- <category2-name>-data.json
|-- <categoryN-name>-data.json
|-- services/
|-- <category1-name>-data.json
|-- <category2-name>-data.json
|-- <categoryN-name>-data.json
I don't know the exactly number of stores, but I know is more than 1500 stores (between 1500~1700), so I'll giving away some stores for free. And you can trust me, I'm the main developer of
BTC-Stores, an open-source Bitcoin directory.
May you ask: why you don't use this data in your website? Firstly, I get all this data because this project, but when I develop this website my friend make me change the focus: now we just accept stores, not services - and the most data of this database is services, not stores.
Well, I think that's all. Any question feel free to ask (:
(just a little p.s: I can change the data structure and the way the files are stored (as I said before) , but we need sometime to talk after the trade-in about what you want change in the database, and you need give me some time to implement it (but not much).)