Code:
$ blender --version
Blender 2.71 (sub 0)
Blender 2.71 (sub 0)
Topic: [ANNOUNCE] BitWrk: Better ways to earn Bitcoins than mining (Read 35126 times)
Sorry, Blender 2.71 is not yet supported. I was on vacation last month, and it will take me a couple of weeks to get the next release done. I recommend that you try with Blender 2.70a!
Code:
bitwrk-blender-0.3.0>$ python3 blender-slave.py --blender /bin/blender
Blender version could not be detected
Blender version could not be detected
Code:
$ uname -a
Linux archaspire 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:34:41 CEST 2014 i686 GNU/Linux
Linux archaspire 3.15.1-1-ARCH #1 SMP PREEMPT Tue Jun 17 09:34:41 CEST 2014 i686 GNU/Linux
Code:
$ blender --version
Blender 2.71 (sub 0)
build date: 2014-06-26
build time: 20:24:22
build commit date: 2014-06-25
build commit time: 20:29
build hash: 772af36
build platform: Linux
build type: Release
build c flags: -Wall -Wcast-align -Werror=declaration-after-statement -Werror=implicit-function-declaration -Werror=return-type -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wnonnull -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wuninitialized -Wredundant-decls -Wno-error=unused-but-set-variable -march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -fopenmp -msse2 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing
build c++ flags: -Wredundant-decls -Wall -Wno-invalid-offsetof -Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wuninitialized -Wundef -Wmissing-declarations -march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -D__STDC_CONSTANT_MACROS -fopenmp -msse2 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing
build link flags: -Wl,--version-script=/build/blender/src/blender-2.71/source/creator/blender.map -pthread
build system: CMake
Blender 2.71 (sub 0)
build date: 2014-06-26
build time: 20:24:22
build commit date: 2014-06-25
build commit time: 20:29
build hash: 772af36
build platform: Linux
build type: Release
build c flags: -Wall -Wcast-align -Werror=declaration-after-statement -Werror=implicit-function-declaration -Werror=return-type -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wnonnull -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wuninitialized -Wredundant-decls -Wno-error=unused-but-set-variable -march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -fopenmp -msse2 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing
build c++ flags: -Wredundant-decls -Wall -Wno-invalid-offsetof -Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wuninitialized -Wundef -Wmissing-declarations -march=i686 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -D__STDC_CONSTANT_MACROS -fopenmp -msse2 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing
build link flags: -Wl,--version-script=/build/blender/src/blender-2.71/source/creator/blender.map -pthread
build system: CMake
Would love to try it out but you need to put out some easy to run software.
Ok, there are now binaries for Windows and OSX on the release page: https://github.com/indyjo/bitwrk/releases/tag/0.3.0
Can you run them?
Interesting project. I had the exact same idea a while back specifically related to Blender. I even started building a front end for it https://github.com/super3/FastF12
Would love to try it out but you need to put out some easy to run software.
Would love to try it out but you need to put out some easy to run software.
Update: BitWrk 0.3.0 "Mercury" has been released! Release announcement here.
BitWrk is rolling along nicely! 
The Blender module has stirred up some attention in the Blender community (e.g., on blenderartists.org and on blendpolis.de) I could still use some help in development.
So, you can help BitWrk in the following ways:
If you like the project you can also donate to Tip4Commit, which encourages participation by paying tips:
I would like to stabilize on the client software and Blender integration, before I start feeding BitWrk with Bitcoin transactions.
The Blender module has stirred up some attention in the Blender community (e.g., on blenderartists.org and on blendpolis.de) I could still use some help in development.
So, you can help BitWrk in the following ways:
- Good: Try out the software, do some Blender rendering, report bugs
- Better: Provide a BitWrk node or two, on a fast computer, providing Blender rendering to the community
- Even better: Participate developing the BitWrk software! Contributions will automatically be paid with some mBTC by Tip4Commit
- Even better: Try to integrate BitWrk into your favorite, compute-intensive application. This is a lot of work but will be rewarded by a share on generated revenue. Please contact me for opportunities!
If you like the project you can also donate to Tip4Commit, which encourages participation by paying tips:
I would like to stabilize on the client software and Blender integration, before I start feeding BitWrk with Bitcoin transactions.
Here is a screenshot of Blender halfway through rendering an image using BitWrk:
New release 20140124
This development release adds experimental support for Blender, the Open Source rendering software. Rendering tasks can be dispatched to the BitWrk service, possibly greatly enhancing rendering times.
Having Blender support could make BitWrk, and also Bitcoin, interesting for new target audiences, like artists, architects, students.
This development release adds experimental support for Blender, the Open Source rendering software. Rendering tasks can be dispatched to the BitWrk service, possibly greatly enhancing rendering times.
Having Blender support could make BitWrk, and also Bitcoin, interesting for new target audiences, like artists, architects, students.
Linux package available
This is good news for users of Arch Linux. There is now a binary package available for you:
https://aur.archlinux.org/packages/bitwrk/
I hope the Open Source community is going to produce more packages soon, for all those wonderful Linux distributions out there. A great way to support this project, by the way. Big thanks to Bradley Pesicka!
This is good news for users of Arch Linux. There is now a binary package available for you:
https://aur.archlinux.org/packages/bitwrk/
I hope the Open Source community is going to produce more packages soon, for all those wonderful Linux distributions out there. A great way to support this project, by the way. Big thanks to Bradley Pesicka!
BitWrk plugged in podcast:
Stephen Sprinkle from morningbit.com has plugged BitWrk for his podcast.
See https://www.youtube.com/watch?v=UHY_Y20Fl4E
Stephen Sprinkle from morningbit.com has plugged BitWrk for his podcast.
See https://www.youtube.com/watch?v=UHY_Y20Fl4E
I too am not 100% happy with the buy/sell terminology, and I am open for suggestions. Both buyers and sellers place bids, so that term would be ambiguous.
Security is a very important factor and your scenario is quite creepy. BitWrk service operators have to keep a close eye on potential security risks.
The system is designed so that selling needs a little more technical expertise than buying, so we should recommend some basic security guidelines.
Security is a very important factor and your scenario is quite creepy. BitWrk service operators have to keep a close eye on potential security risks.
The system is designed so that selling needs a little more technical expertise than buying, so we should recommend some basic security guidelines.
It is! It's basically crowdsourcing computing power.
I found the Buy/Sell terminology confusing. Perhaps that could be changed to Jobs/Bids?
Also, are you thinking of system that sends the worker application to client computers?
Have you thought of the possibility of this being used to make a botnet or distribute malicious software? For instance what if worker application was actually cryptolocker and it simply ran for a few minutes at high speed (to look like a legitimate application) but instead encrypts the users home directory? The attacker would simply pay 330uBTC to deliver their payload.
Perhaps there needs to be an approval process before a worker application is allowed onto the network.
I found the Buy/Sell terminology confusing. Perhaps that could be changed to Jobs/Bids?
Also, are you thinking of system that sends the worker application to client computers?
Have you thought of the possibility of this being used to make a botnet or distribute malicious software? For instance what if worker application was actually cryptolocker and it simply ran for a few minutes at high speed (to look like a legitimate application) but instead encrypts the users home directory? The attacker would simply pay 330uBTC to deliver their payload.
Perhaps there needs to be an approval process before a worker application is allowed onto the network.
Edit: Aha, it is working now. I have no idea why. All I have done is walk away and come back later and restart my computer a time or two. Oh well! I'm thinking of making some applications to sell. This is exciting!
Edit 2: And there you are with your 333 uBTC buy! You're working my poor computer to death LOL
Ahh, that made my day :-)Edit 2: And there you are with your 333 uBTC buy! You're working my poor computer to death LOL
Please go ahead and embed BitWrk support into your favorite software. It's not very difficult from a programming point of view. The hard part is done by the BitWrk client. I can provide you with all necessary documentation, will just need some time to write it.
Do you know what I really like about BitWrk? If all works out, it could be a whole new business model for open source software.
I'll be running buy orders for uBTC 333 for a couple of hours. The 500 error code is just what the raytracer is seeing. You can see what's really going wrong in the client's console. Yes, I know that's inconvenient!
WRT to port forwarding, looks like there is still something blocking port 8082. What does http://www.yougetsignal.com/tools/open-ports/ say?
Edit: Oh, and I am seeing this error in the server's log:
Quote
Invalid price satoshi 10, must be >= uBTC 10
I just ran the client and did not see your buy orders.
8082 is open according to yougetsignal.com
Yes the satoshi error was me messing around but I fixed that because I got an error on my end as well.
I think the problem is that the master is trying to connect and receive info from the slave. However the slave and the master are on the same ip address and that creates an issue.
Edit: Aha, it is working now. I have no idea why. All I have done is walk away and come back later and restart my computer a time or two. Oh well! I'm thinking of making some applications to sell. This is exciting!
Edit 2: And there you are with your 333 uBTC buy! You're working my poor computer to death LOL
This sounds great, though this is a very difficult project but at least as important. I hope you all the best with this and I'll keep watching this.
Alright so I decided to try this out.
Cool!
Quote
I got the client compiled and running as well as net.bitwrk/gorays/0. I also made sure to port forward port 8082. I saw that there were no current buy orders on the server so I decided to run the net.bitwrk/gorays/0 as master. But, it keeps saying "Got status code 500 (500 Internal Server Error)". Do you know why?
I'll be running buy orders for uBTC 333 for a couple of hours. The 500 error code is just what the raytracer is seeing. You can see what's really going wrong in the client's console. Yes, I know that's inconvenient!
WRT to port forwarding, looks like there is still something blocking port 8082. What does http://www.yougetsignal.com/tools/open-ports/ say?
Edit: Oh, and I am seeing this error in the server's log:
Quote
Invalid price satoshi 10, must be >= uBTC 10
Alright so I decided to try this out.
I got the client compiled and running as well as net.bitwrk/gorays/0. I also made sure to port forward port 8082. I saw that there were no current buy orders on the server so I decided to run the net.bitwrk/gorays/0 as master. But, it keeps saying "Got status code 500 (500 Internal Server Error)". Do you know why?
Also I tried to run a slave to do the work the my master had created, however the client keeps saying
2013/12/06 09:54:02 Error receiving result from BitWrk network: Error transmitting work and receiving encrypted result: Error fetching request &{POST http://xx.xxx.xxx.xxx::8082/ef9163af HTTP/1.1 1 1 map[User-Agent:[BitWrkGoClient/0.0.1] Content-Type:[multipart/form-data; boundary=7293f83d9824dae8c9a1b9b7fe1fd67558fb9f5
e8c5f6111ffbe2d92b424]] 0xc084108f30 0 [] false xx.xxx.xxx.xxx::8082 map[] map[]
map[] }: Post http://xx.xxx.xxx.xxx::8082/ef9163af: dial tcp xx.xxx.xxx.xxx:8082: ConnectEx tcp: No connection could be made because the target machine actively refused it.
2013/12/06 09:54:02 Temporary disposed: 243e20170658331cc17bf444afe0ced18d6f0184
22e35d781a2d1290c2ed3a7d
The x's are to hide my ip address.
I got the client compiled and running as well as net.bitwrk/gorays/0. I also made sure to port forward port 8082. I saw that there were no current buy orders on the server so I decided to run the net.bitwrk/gorays/0 as master. But, it keeps saying "Got status code 500 (500 Internal Server Error)". Do you know why?
Also I tried to run a slave to do the work the my master had created, however the client keeps saying
2013/12/06 09:54:02 Error receiving result from BitWrk network: Error transmitting work and receiving encrypted result: Error fetching request &{POST http://xx.xxx.xxx.xxx::8082/ef9163af HTTP/1.1 1 1 map[User-Agent:[BitWrkGoClient/0.0.1] Content-Type:[multipart/form-data; boundary=7293f83d9824dae8c9a1b9b7fe1fd67558fb9f5
e8c5f6111ffbe2d92b424]] 0xc084108f30 0 [] false xx.xxx.xxx.xxx::8082 map[] map[]
2013/12/06 09:54:02 Temporary disposed: 243e20170658331cc17bf444afe0ced18d6f0184
22e35d781a2d1290c2ed3a7d
The x's are to hide my ip address.
I think a web of trust is viable, but proving arbitrary computational work was done with zero trust is not.
Well, computational work will not be arbitrary, but defined by a rigid specification how to compute the result from a given input. This is what the "article ID" is used for in BitWrk: specifying which kind of computation to perform.Apart from dummy article IDs like "foobar", currently the only valid one is net.bitwrk/gorays/0:
- net.bitwrk is the namespace prefix I will use for my articles, i.e. software I integrate into BitWrk.
- gorays is the name of the sample application (the raytracer I mentioned).
- 0 is the version of the article specification, in order to remain compatible. Whenever I break backwards compatibility, I will assign a new version number.
- There might be more suffixes later, e.g. to specify a maximum complexity class.
If I do a certain amount of computational work for another party, how do I prove I did it?
The buyer has posted a hash sum of the work data. You post a hash sum of the result to the publicly visible transaction log. Equal work must (by BitWrk's specification) lead to an equal result. All messages are cryptographically signed.So the buyer of the computer time would have to know what the result of the work was before-hand?
In case of a dispute, the correctness of the computation can be verified by a third party. The third party could be a computer owned by the BitWrk service operator (who must be trusted in anyway) or by the market itself (this hasn't been decided on yet).
Losing a dispute will be punished by reputation loss. Good reputation will be rewarded with lower fees.
I think a web of trust is viable, but proving arbitrary computational work was done with zero trust is not. If I do a certain amount of computational work for another party, how do I prove I did it?
The buyer has posted a hash sum of the work data. You post a hash sum of the result to the publicly visible transaction log. Equal work must (by BitWrk's specification) lead to an equal result. All messages are cryptographically signed.In case of a dispute, the correctness of the computation can be verified by a third party. The third party could be a computer owned by the BitWrk service operator (who must be trusted in anyway) or by the market itself (this hasn't been decided on yet).
Losing a dispute will be punished by reputation loss. Good reputation will be rewarded with lower fees.
Jump to: