#2
You can actually recreate OpenBazaar as an Evolution app without needing most of the OB infrastructure.
That's awesome news.
#2
You can actually recreate OpenBazaar as an Evolution app without needing most of the OB infrastructure.
Is it what the average Joe should do?#2
You can actually recreate OpenBazaar as an Evolution app without needing most of the OB infrastructure.
"Or is it meant that the developers take care of it? Since you are one of those developers, how buyers/sellers can be protected from fraud in DASH Evolution? OpenBazaar uses multisignatures and moderators."
Both multisig and moderation is in the Evolution roadmap but we haven't finished designs for V1 so can't give you a final answer yet. OB isn't something we would be building but 3rd party devs could using DAPI. What we are building is the platform to develop apps on, the actual apps will be made by 3rd parties. We will make some official apps like Wallet, merchant sample, social functions for launch though.
"AndyDark, could you please help me with the Python import error I reported several days ago?"
I didn't work on the Python implementation so maybe someone else can help you, very busy on completing Evolution design at the minute. I will post a message on Slack for you though to ask if anyone else can answer.
Can you make a poker lobby on it?
#2
You can actually recreate OpenBazaar as an Evolution app without needing most of the OB infrastructure.
Is it what the average Joe should do?
Or is it meant that the developers take care of it? Since you are one of those developers, how buyers/sellers can be protected from fraud in DASH Evolution? OpenBazaar uses multisignatures and moderators.
AndyDark, could you please help me with the Python import error I reported several days ago?
Thanks, I tried it already.Can you get the Bitcoin version of Electrum running ok? I had a few dependency problems that took a bit of time to track down.
EDIT: For the coinhash module, it's an included module but you need to run "setup.py install" before running Electrum.
$ sudo python setup.py install
running install
running bdist_egg
running egg_info
creating Electrum_DASH.egg-info
writing requirements to Electrum_DASH.egg-info/requires.txt
writing Electrum_DASH.egg-info/PKG-INFO
writing top-level names to Electrum_DASH.egg-info/top_level.txt
writing dependency_links to Electrum_DASH.egg-info/dependency_links.txt
writing manifest file 'Electrum_DASH.egg-info/SOURCES.txt'
error: package directory 'electrum_dash_gui' does not exist
Thanks, I tried it already.
Code:$ sudo python setup.py install running install running bdist_egg running egg_info creating Electrum_DASH.egg-info writing requirements to Electrum_DASH.egg-info/requires.txt writing Electrum_DASH.egg-info/PKG-INFO writing top-level names to Electrum_DASH.egg-info/top_level.txt writing dependency_links to Electrum_DASH.egg-info/dependency_links.txt writing manifest file 'Electrum_DASH.egg-info/SOURCES.txt' error: package directory 'electrum_dash_gui' does not exist
Interestingly, I managed to install and run the DASH electrum from the source ( https://github.com/dashpay/electrum-dash ).
sudo apt-get install python-dev python-pip libudev-dev libusb-1.0.0-dev
sudo pip install cython
sudo pip install hidapi
sudo apt-get install python-websocket
pyrcc4 icons.qrc -o gui/qt/icons_rc.py
sudo python setup.py sdist
sudo pip install --pre dist/Electrum-DASH-2.4.1rc2.tar.gz
./electrum-dash
Actually I have contacted OB development team and asked about the possibility of Dash integration few weeks ago.
They told me that current OB architecture is very closely integrated with BTC - it is literally hard-coded there. OB is not designed in a way to integrate other currencies and it looks like the only possibility to integrate Dash into it is a fork.
Will Evo support multi-user accounts for merchants or "joint" end-user accounts (think married couples)? I'm thinking that merchants will require more than one login and potentially multiple sign-offs in order to authorize outgoing transactions. Some users for merchant accounts might even be read-only access (like an accountant login). For that you would need administrator rights to the overall account to authorize user access to certain capabilities.
I just want to insert that thinking early in the process... even if not supported right away, I would encourage you to plan for that in the future and to design the architecture in such a way that will enable that down the road. Perhaps PayPal merchant accounts or business bank accounts would be a good model to design from?
setup.py install did not succeed, as I reported above, and so it could not have fixed anything. ./electrum-dash still crashes with an import error.I did a little bit of digging around and found this: https://github.com/mazaclub/encompass/issues/95. Seems somewhat related, though strange that setup.py install didn't fix the issue. It was still giving that error after running setup.py install?
Will Evo support multi-user accounts for merchants or "joint" end-user accounts (think married couples)? I'm thinking that merchants will require more than one login and potentially multiple sign-offs in order to authorize outgoing transactions. Some users for merchant accounts might even be read-only access (like an accountant login). For that you would need administrator rights to the overall account to authorize user access to certain capabilities.
I just want to insert that thinking early in the process... even if not supported right away, I would encourage you to plan for that in the future and to design the architecture in such a way that will enable that down the road. Perhaps PayPal merchant accounts or business bank accounts would be a good model to design from?
I don't like the way OB works, with the doubling up of payments, etc... there should be an easier way, but aside from that, I still desperately desire to see Dash build a marketplace that is hosted on the MN network's sharded storage, so it can be accessed by users as easily as ebay. Illegal sales could be reported and deleted (community regulated) which *should* keep masternodes safe legally. have a small fee off the total sale go to the MNs for hosting, and it's win-win.
Sorry, it's my dearest hope so I keep bringing it up
Along these lines how hard would it be to implement contracts? (ether and gas could be just that....poof!)
Take a look at Braintree (a PayPal company) too. They started after Stripe, but they have been outgrowing them. The model and API are very very similar, but they are doing a few things differently that you might find helpful. Really happy that you are using these as models! They are all the best in the industry. If you make life easy for programmers and gateway service providers to integrate, it really helps with adoption.Hi babygiraffe. That's a good point, we could fit HD multisignature in to the current account structure without much trouble. We also have plans for different levels of authorization built into the auth protocol.
We've been trying out PayPal and Google Wallet but actually Stripe would be the closest to our strategy as it's the easiest to use and least hassle for users. Our first DashPay feature will just be a 'pay with Dash' button though without any frills, but we can build those up and have planned most of that out when designing the architecture.