I installed it on Windows 7 but I had to manually find the following dll files and place them in the Open-Transactions folder:
qt5widgets.dll
qt5gui.dll
qt5core.dll
libglesv2.dll
icuin51.dll
icuuc51.dll
icudt51.dll
But now I'm getting the following error when I try to run moneychanger-qt.exe:
"The procedure entry point ?viewportSizeHint@QTableView@@MBE?AVQSize@@XZ could not be located in the dynamic link library Qt5Widgets.dll."
I'm guessing I must have the wrong version of qt5widgets.dll or something?
Topic: Moneychanger (Windows Builds) - Out of Date! - page 2. (Read 59483 times)
New Release, including C++ QT Moneychanger!
Woho! Checkout the OP!
Nice job done.Woho! Checkout the OP!
Quote
Windows:
Code:
SHA256(Open-Transactions-0.90.c-Win32-setup.zip)= b2a74a88283c86bfdeda3de94ed9850758e5d6b8ecf3c6274d4e078d8d666264
Code:
SHA256(Open-Transactions-0.90.c-Win32-setup.zip)= b2a74a88283c86bfdeda3de94ed9850758e5d6b8ecf3c6274d4e078d8d666264
What checksum utility do you use to verify a SHA256 hash on Windows?
New Release, including C++ QT Moneychanger!
Woho! Checkout the OP!
Woho! Checkout the OP!
Mega is obviously a no go in a work environment.
Found a work around.
fgrep -nR "main_show_basket" scripts/*
scripts/ot/ot_commands.ot:52:def main_show_basket()
Looks like main_show_basket() is on line 52 of the file "ot_commands.ot"
Perhaps you have an old version of this file?
You might see if there are multiple copies on your system, and also pull it up and make sure that function exists on line 52.
There are 2 files. But it seems i already have the newest file in the needed place. So the file that is referencind the function must be the problem. But i dont see why it doesnt work when its taken from the original linux version... and i wonder why it doesnt work for me but for the win-version-dev... did any other user try it?
fgrep -nR "main_show_basket" scripts/*
scripts/ot/ot_commands.ot:52:def main_show_basket()
Looks like main_show_basket() is on line 52 of the file "ot_commands.ot"
Perhaps you have an old version of this file?
You might see if there are multiple copies on your system, and also pull it up and make sure that function exists on line 52.
Looks like i did it wrong first with the sample data. I now renamed the old setting-dir and used a new one. I copied in there the content of sample-data/ot-sample-data and started. It seems it founds server, nym, acct and purse but got an error then:
I dont find a file with that name so i think it might be a missing class in the code.
Code:
Welcome to Open Transactions -- version 0.89.q
Using as server: r1fUoHwJOWCuK3WBAAySjmKYqsG6G2TYIxdqY6YNuuG
Using as mynym: DYEB6U7dcpbwdGrftPnslNKz76BDuBTFAjiAgKaiY2n
Using as myacct: yQGh0vgm9YiqYOh6bfLDxyAA7Nnh2NmturCQmOt4LTo
Using as mypurse: JY7kEFnm2c50CGNphdpgnlVo2hOZuLrBua5cFqWWR9Q
OTScriptChai::ExecuteScript:
Caught chaiscript::exception::eval_error:
Can not find object: main_show_basket.
File:
Start position, line: 0 column: 0
End position, line: 0 column: 0
Error: "Can not find object: main_show_basket" during evaluation at (430, 39)
from scripts\opentxs (412, 26) :
from scripts\opentxs (412, 9) :
from scripts\opentxs (622, 1) :
C:\T_I\Geld\Open-Transactions>
Using as server: r1fUoHwJOWCuK3WBAAySjmKYqsG6G2TYIxdqY6YNuuG
Using as mynym: DYEB6U7dcpbwdGrftPnslNKz76BDuBTFAjiAgKaiY2n
Using as myacct: yQGh0vgm9YiqYOh6bfLDxyAA7Nnh2NmturCQmOt4LTo
Using as mypurse: JY7kEFnm2c50CGNphdpgnlVo2hOZuLrBua5cFqWWR9Q
OTScriptChai::ExecuteScript:
Caught chaiscript::exception::eval_error:
Can not find object: main_show_basket.
File:
Start position, line: 0 column: 0
End position, line: 0 column: 0
Error: "Can not find object: main_show_basket" during evaluation at (430, 39)
from scripts\opentxs (412, 26) :
from scripts\opentxs (412, 9) :
from scripts\opentxs (622, 1) :
C:\T_I\Geld\Open-Transactions>
I dont find a file with that name so i think it might be a missing class in the code.
As I'm sure I said before, you need to show me that you have it working with the test data, before you try other contracts such as digitalis.
Find your data folder, and wipe it clean. Then copy the test data into that folder. Then try the OT commands I mentioned.
ONLY if those commands are working with the test data, THEN you can start using other data such as the digitalis contract.
Find your data folder, and wipe it clean. Then copy the test data into that folder. Then try the OT commands I mentioned.
ONLY if those commands are working with the test data, THEN you can start using other data such as the digitalis contract.
What happens when you do these commands:
run_opentxs.bat list
run_opentxs.bat list
Code:
C:\T_I\Geld\Open-Transactions\scripts>run_opentxs.bat list
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContrac
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContrac
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
run_opentxs.bat showaccounts
Code:
C:\T_I\Geld\Open-Transactions\scripts>run_opentxs.bat showaccounts
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContract
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContract
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
run_opentxs.bat balance
Code:
C:\T_I\Geld\Open-Transactions\scripts>run_opentxs.bat balance
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContract
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
Welcome to Open Transactions -- version 0.89.q
OTCachedKey::GetMasterPassword: Please enter your password.
Passphrase request for: "Loading private key from credential."
(OT) passphrase:
UNKNOWN element type in OTContract::LoadContractXML: notaryProviderContract, value: notaryProviderContract
UNKNOWN element type in OTContract::LoadContractXML: notaryServer, value: notaryServer
Unable to find a server contract to use. Please use the option: --server SERVER_ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
etc.
I'm also assuming you are using the test data...
I couldnt make the test data run like i posted 2 post ago in this thread. So i made a personal account with Nym (since then i have to login always), the server contract for digitalis (the problem before were the linux linebreaks. I didnt think that the xml-format is not able to understand missing linebreaks.) and i inserted all coins that server can handle. So i think it should work fine. It works too, but not for commands that have options.
What happens when you do these commands:
run_opentxs.bat list
run_opentxs.bat showaccounts
run_opentxs.bat balance
etc.
I'm also assuming you are using the test data...
run_opentxs.bat list
run_opentxs.bat showaccounts
run_opentxs.bat balance
etc.
I'm also assuming you are using the test data...
I now tried to run without testserver since i didnt get it to work but the shell seems to have problems following some commands. For example showmarkets is not working even with correct syntax. I wrote it up with that post and following: https://bitcointalksearch.org/topic/m.3220613
I hope theres a solution. I see its not easy to set this up and i hope this project goes on to a status where normal people can use it. Till now i unfortunately only read people that state they tried to set it up and gave up at the end. I dont want to give up, though i ask myself if there are happening trades at all on digitalis when its so hard to set it up.
I hope theres a solution. I see its not easy to set this up and i hope this project goes on to a status where normal people can use it. Till now i unfortunately only read people that state they tried to set it up and gave up at the end. I dont want to give up, though i ask myself if there are happening trades at all on digitalis when its so hard to set it up.
Thank-you for your reply's.
I've made an updated release of Open Transactions for windows. (0.89.q)
The test-data is available for download here:
https://github.com/FellowTraveler/Open-Transactions/archive/master.zip
You need to copy it into the %APPDATA%/OpenTransactions dir.
You will also need to run the otserver.exe
I've made an updated release of Open Transactions for windows. (0.89.q)
The test-data is available for download here:
https://github.com/FellowTraveler/Open-Transactions/archive/master.zip
You need to copy it into the %APPDATA%/OpenTransactions dir.
You will also need to run the otserver.exe
Thanks for creating the new version. I now tried to set it up. I installed 0.89 64bit. Then deleted all in appdata OT and copied the content of master.zip into. When i then start OT and run stat it shows me there are no pseudonyms, servers, assets or accounts.
I then thought its because i have to start otserver.exe. When i do this it says:
Code:
Welcome to Open Transactions... Test Server -- version 0.89.q
(transport build: OTMessage -> OTEnvelope -> ZMQ )
The Winsock 2.2 dll was found okay
Now loading the server nym, which will also ask you for a password, to unlock
its private key.
Using Wallet: notaryServer.xml
Failed trying to open data locking file (to store PID 3804): C:/Users/Sebastian/
AppData/Roaming/OpenTransactions/server_data/ot.pid
OTPaths::BuildFolderPath: Made new folder: C:/Users/Sebastian/AppData/Roaming/Op
enTransactions/server_data/
==> WARNING: Main file not found. To create it, continue this process now...
REQUIREMENTS: You must already have a wallet, where you have created one Nym.
This will be a temporary wallet only, for the purpose of generating the server
nym and the master key for that server nym. You can erase the contents of the
~/.ot/client_data folder once we are done with this process, and the OT client
will just create a fresh wallet to replace it. In other words, don't continue
to use the temporary wallet as a REAL wallet, since it contains the master
key and private key for your new server nym. We're using a temporary client-side
wallet for the convenience of generating the server nym--we'll copy it over to
the server side, and then we'll wipe the temp wallet and start with a fresh one
once this process is done.
(FYI, you can decode an armored wallet by using the 'opentxs decode' command.)
-- You must also have the new Server Nym's "NymID", which should be found in the
wallet.
-- When you have created your server Nym (using your temp wallet) you will want
to
copy the credentials from the temp wallet to your new server:
cp -R ~/.ot/client_data/credentials ~/.ot/server_data/
-- You must already have a signed server contract. (*** To get one, copy the
UNSIGNED version of the sample server contract, which is named 'localhost.xml',
and then change the tags as you see fit. Then use the same Nym, the server Nym,
to sign the server contract, via the 'opentxs newserver' command.***)
You must also have the server ID for the above contract, which the newserver
command will output at the same time it outputs the newly-signed server contract
.
=> Note that the Nym who signs the server contract MUST be the same Nym that you
provide HERE, for this process now...)
-- Finally, you must provide the cached key from the same wallet where you broug
ht
the Nym from (In this case, be careful to only copy the base64-encoded portion
of the cached key from the wallet, and not the XML tags around it!) We
recommend you create a blank wallet entirely for this purpose (of generating
that cached key and server Nym, to be used for your new OT server.) Then erase i
t
once this process is done.
==> WARNING: Main file not found. To create it, continue this process now...
Enter the ServerID for your server contract:
(transport build: OTMessage -> OTEnvelope -> ZMQ )
The Winsock 2.2 dll was found okay
Now loading the server nym, which will also ask you for a password, to unlock
its private key.
Using Wallet: notaryServer.xml
Failed trying to open data locking file (to store PID 3804): C:/Users/Sebastian/
AppData/Roaming/OpenTransactions/server_data/ot.pid
OTPaths::BuildFolderPath: Made new folder: C:/Users/Sebastian/AppData/Roaming/Op
enTransactions/server_data/
==> WARNING: Main file not found. To create it, continue this process now...
REQUIREMENTS: You must already have a wallet, where you have created one Nym.
This will be a temporary wallet only, for the purpose of generating the server
nym and the master key for that server nym. You can erase the contents of the
~/.ot/client_data folder once we are done with this process, and the OT client
will just create a fresh wallet to replace it. In other words, don't continue
to use the temporary wallet as a REAL wallet, since it contains the master
key and private key for your new server nym. We're using a temporary client-side
wallet for the convenience of generating the server nym--we'll copy it over to
the server side, and then we'll wipe the temp wallet and start with a fresh one
once this process is done.
(FYI, you can decode an armored wallet by using the 'opentxs decode' command.)
-- You must also have the new Server Nym's "NymID", which should be found in the
wallet.
-- When you have created your server Nym (using your temp wallet) you will want
to
copy the credentials from the temp wallet to your new server:
cp -R ~/.ot/client_data/credentials ~/.ot/server_data/
-- You must already have a signed server contract. (*** To get one, copy the
UNSIGNED version of the sample server contract, which is named 'localhost.xml',
and then change the tags as you see fit. Then use the same Nym, the server Nym,
to sign the server contract, via the 'opentxs newserver' command.***)
You must also have the server ID for the above contract, which the newserver
command will output at the same time it outputs the newly-signed server contract
.
=> Note that the Nym who signs the server contract MUST be the same Nym that you
provide HERE, for this process now...)
-- Finally, you must provide the cached key from the same wallet where you broug
ht
the Nym from (In this case, be careful to only copy the base64-encoded portion
of the cached key from the wallet, and not the XML tags around it!) We
recommend you create a blank wallet entirely for this purpose (of generating
that cached key and server Nym, to be used for your new OT server.) Then erase i
t
once this process is done.
==> WARNING: Main file not found. To create it, continue this process now...
Enter the ServerID for your server contract:
When i copied the sample data shouldnt it run automatically with that data? It asks for serverid, server user id and cached key and so on.
I thought i will test on testserver a bit and then try to connect to markm's server to check out the assets there are traded...
Thank-you for your reply's.
I've made an updated release of Open Transactions for windows. (0.89.q)
The test-data is available for download here:
https://github.com/FellowTraveler/Open-Transactions/archive/master.zip
You need to copy it into the %APPDATA%/OpenTransactions dir.
You will also need to run the otserver.exe
I've made an updated release of Open Transactions for windows. (0.89.q)
The test-data is available for download here:
https://github.com/FellowTraveler/Open-Transactions/archive/master.zip
You need to copy it into the %APPDATA%/OpenTransactions dir.
You will also need to run the otserver.exe
Oh... quit... i tried exit, close and so on... but quit works. I probably work too less with command lines...
run_opentxs addserver doesnt work too. The result is only:
Regarding testdata... there is no such directories. I found a dir ot and one named samples that might be this. I copied the content of samples into ot but it still isnt finding anything.
Ill start a new thread in the other forum now...
run_opentxs addserver doesnt work too. The result is only:
Code:
C:\***\Open-Transactions\scripts>run_opentxs addserver
Welcome to Open Transactions -- version 0.89.f
Unable to find a server contract to use. Please use the option: --server SERVER_
ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
Welcome to Open Transactions -- version 0.89.f
Unable to find a server contract to use. Please use the option: --server SERVER_
ID
(Where SERVER_ID is the Server's ID. Partial matches ARE accepted.)
Unable to find My Nym. Please use the option: --mynym USER_ID
(Where USER_ID is the Nym's ID. Partial matches and names are accepted.)
.
..
...
....
.....
opentxs>
Regarding testdata... there is no such directories. I found a dir ot and one named samples that might be this. I copied the content of samples into ot but it still isnt finding anything.
Ill start a new thread in the other forum now...
Yes i closed simply the cmd-window since i didnt find a command to quit OT.
Did you try "quit" ?
(In any case, you shouldn't have to quit OT anyway since you should be running opentxs separately each time you do a command.)
I suggest you take this conversation to the opentransactions.org/forum or the OT IRC channel, which are both more appropriate venues for OT-related tech support than the Bitcoin project dev board.
Quote
But i tried now what you suggested. I went into the scripts folder and used the command you gave. But it doesnt recognize the command. I checked and found that there is a file named opentxs but is has no file-ending like .exe or bat. OT normally is started with a batchfile run_opentxs that is located in scripts-folder.
Okay then, did you try "run_opentxs addserver" instead of "opentxs addserver" ?
Quote
Then i wanted to try the localhost contract but i cant find that contract. I searched for the string notaryprovidercontract in all files in the OT-Dir and i searched with google but only found an incomplete contract. Arent these included in the windows build or are they already compiled somehow so that i can start it somehow?
I suggest you do this:
1. Make sure the server isn't running.
2. Make sure the client isn't running.
3. Copy the TEST DATA into the actual data location, so you can run the server and client using the TEST DATA.
4. On linux this is done like this: rm -rf ~/.ot/* && cp -R Open-Transactions/sample-data/ot-sample-data/* ~/.ot
I don't remember where Windows keeps the data but basically you will want to wipe the files at that location, and then copy the sample data into it.
Then you can start the server and client, and play around using the sample data. So you will not have to "addserver" the localhost contract, because in the sample data, it's ALREADY set up.
Yes i closed simply the cmd-window since i didnt find a command to quit OT. But i tried now what you suggested. I went into the scripts folder and used the command you gave. But it doesnt recognize the command. I checked and found that there is a file named opentxs but is has no file-ending like .exe or bat. OT normally is started with a batchfile run_opentxs that is located in scripts-folder. It says:
So i tried going one dir above and used ot addserver. Ot starts but doesnt accept the addserver-command.
I wonder if there is a clean way to close OT at all in windows at the moment. Since even when i would start it from command-shell the window would open and i only would be able to close this window which most probably would leave the file behind.
Then i wanted to try the localhost contract but i cant find that contract. I searched for the string notaryprovidercontract in all files in the OT-Dir and i searched with google but only found an incomplete contract. Arent these included in the windows build or are they already compiled somehow so that i can start it somehow?
Code:
@echo off
set START_DIR="%cd%"
cd /D %~dp0..\
ot.exe scripts\opentxs
cd /D %START_DIR%
set START_DIR="%cd%"
cd /D %~dp0..\
ot.exe scripts\opentxs
cd /D %START_DIR%
So i tried going one dir above and used ot addserver. Ot starts but doesnt accept the addserver-command.
I wonder if there is a clean way to close OT at all in windows at the moment. Since even when i would start it from command-shell the window would open and i only would be able to close this window which most probably would leave the file behind.
Then i wanted to try the localhost contract but i cant find that contract. I searched for the string notaryprovidercontract in all files in the OT-Dir and i searched with google but only found an incomplete contract. Arent these included in the windows build or are they already compiled somehow so that i can start it somehow?
This is why I said to make sure it is working first with the test data.
If it's working fine with the test data, then the problem becomes markm's contract.
But if it's not even working with the test data, then the problem becomes OT.
If markm's contract turns out to be the only one that doesn't work, then you might be right about him running an old version of OT.
But if all test contracts fail, then the problem would have more to do with the way OT parses EOF on Windows.
The existing clients (iPhone client, command-line client, java test GUI) all delete the client pid file automatically during a proper shutdown.
So you will only see that problem if you are killing the client without allowing it to shutdown gracefully.
Normally that PID file exists in order to prevent you from running two wallets simultaneously against the same data. (Which could corrupt the data.)
Try NOT using the opentxs prompt, but instead ONLY use it from the UNIX command line.
For example, don't do "opentxs" and then "addserver" -- instead do "opentxs addserver" directly from the UNIX command line.
Then you will no longer see the PID problem.
If it's working fine with the test data, then the problem becomes markm's contract.
But if it's not even working with the test data, then the problem becomes OT.
If markm's contract turns out to be the only one that doesn't work, then you might be right about him running an old version of OT.
But if all test contracts fail, then the problem would have more to do with the way OT parses EOF on Windows.
Quote
how do i close OT without having to delete next time the file: ot.pid first in client_data to run OT?
The existing clients (iPhone client, command-line client, java test GUI) all delete the client pid file automatically during a proper shutdown.
So you will only see that problem if you are killing the client without allowing it to shutdown gracefully.
Normally that PID file exists in order to prevent you from running two wallets simultaneously against the same data. (Which could corrupt the data.)
Try NOT using the opentxs prompt, but instead ONLY use it from the UNIX command line.
For example, don't do "opentxs" and then "addserver" -- instead do "opentxs addserver" directly from the UNIX command line.
Then you will no longer see the PID problem.
you should be pasting the entire otc file when doing addserver command.
I do.
I start OT. Then i get opentxs> and type addserver + enter.
It tells me "please paste as server contract, followed by an EOF or a ~ by itself on a blank line:
I then open DigitalisOTserver.otc i downloaded from markm. I copy the content:
Code:
-----BEGIN SIGNED CONTRACT-----
Hash: SAMY
email="[email protected]"
serverURL="http://sourceforge.net/p/galacticmilieu/home/Home/"/>
URL="http://sourceforge.net/p/galacticmilieu/home/Home/" />
Neither Digitalis Data Services, nor SourceForge, actually issue the
currencies or digital assets, and they do not back any of the same.
You are solely responsible for whom you choose to trade with.
Open Transactions software is open source, and
code audits are randomly performed by hackers in the
open source community. Fellow Traveler (the author of the
software) also uses Valgrind.
Hopefully at some point some kind of fee structure will be
implemented to support the running of the server. Possibly
something similar to loom's usage-tokens but if so we would
probably use bitNicKeLs for the purpose (as that is the kind
of purpose for which bitNicKeLs were intended).
Issuers are solely liable to perform according to
the conditions specified in their asset contracts.
Float - the total quantity of any digital asset outstanding -
is created by the issuer from his own mint, and signed by his
private key.
Disbursements from the Mint account are to be made on receipt of
duly signed and public authorization from the Issuer. All
disbursements from the Mint account are to be made to the single
Currency Comptroller account identified by the authorization.
From time to time, the Currency Comptroller may direct the
Currency Manager to return digital assets to the Mint
for the express purpose of reducing the float. Digital assets
so delivered are to be deposited into the Mint account,
thus reducing the float by that amount.
The purchase, redemption and trading at Digitalis OT server
normally are done on the basis of strong privacy. We try to
never release any of your information unless compelled by law.
- -----BEGIN CERTIFICATE-----
MIICPzCCAaigAwIBAgIBADANBgkqhkiG9w0BAQQFADAlMQswCQYDVQQGEwJVSzEW
MBQGA1UEAxMNT3BlblNTTCBHcm91cDAeFw0xMTEyMDQwNTM2MjdaFw0yMTEyMDEw
NTM2MjdaMCUxCzAJBgNVBAYTAlVLMRYwFAYDVQQDEw1PcGVuU1NMIEdyb3VwMIGf
MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCvjeMKIacyh7LyVwaxHopSa0EY0SdD
hVeXRFQ+JyvRcTp2CBOFuUZ9mx7MgSyblaZssue/C6CdMtuJfabQgUHhK2zaArx6
rrvQ57SHH4p38xmVG8frD22pS4/wF+M2tmt6yCj9kxTLY6cWPve70gf1HE6sS4BJ
gl2uM8ZcDr5deQIDAQABo38wfTAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQE
AwIBBjAdBgNVHQ4EFgQUBti7sfjamiXcNkp/WSir5iOauo0wEQYJYIZIAYb4QgEB
BAQDAgIEMCgGCWCGSAGG+EIBDQQbFhlleGFtcGxlIGNvbW1lbnQgZXh0ZW5zaW9u
MA0GCSqGSIb3DQEBBAUAA4GBAFZ4UxLkWRWvpcpqEs+jATB+2c1X7g2m00+7IXjv
2WG99F0I+ZGWmuowaxnzMAOmTNXFYplEKPYeoYjWaVOaqDq2L+bsaP6SxJDn/+wW
xGBJFBqNqzH8VkLQf/8lhuE8FMsX7H1k94Q2pACRGUZRRGaPlmV0fcx5/zCnhvcQ
wmkq
- -----END CERTIFICATE-----
-----BEGIN CONTRACT SIGNATURE-----
Version: Open Transactions 0.75
Comment: http://github.com/FellowTraveler/Open-Transactions/wiki
CoABFojWQphmaNv2WOIsGuvvqtO4zIJS74K9+rieHoeJ7jNu9SGFgPhvIPw84Ghi
ual/poyRK870Fs2y2T9dMctWiuj+D3+2bURcLfv/Kz3wXmldGfV9UAeYQhlVSkIv
BMyUqVu6LIIDle9CUFRICjNohX89qCr55b+Wqvcppbj7oEY=
-----END CONTRACT SIGNATURE-----
Hash: SAMY
email="[email protected]"
serverURL="http://sourceforge.net/p/galacticmilieu/home/Home/"/>
URL="http://sourceforge.net/p/galacticmilieu/home/Home/" />
Neither Digitalis Data Services, nor SourceForge, actually issue the
currencies or digital assets, and they do not back any of the same.
You are solely responsible for whom you choose to trade with.
Open Transactions software is open source, and
code audits are randomly performed by hackers in the
open source community. Fellow Traveler (the author of the
software) also uses Valgrind.
Hopefully at some point some kind of fee structure will be
implemented to support the running of the server. Possibly
something similar to loom's usage-tokens but if so we would
probably use bitNicKeLs for the purpose (as that is the kind
of purpose for which bitNicKeLs were intended).
Issuers are solely liable to perform according to
the conditions specified in their asset contracts.
Float - the total quantity of any digital asset outstanding -
is created by the issuer from his own mint, and signed by his
private key.
Disbursements from the Mint account are to be made on receipt of
duly signed and public authorization from the Issuer. All
disbursements from the Mint account are to be made to the single
Currency Comptroller account identified by the authorization.
From time to time, the Currency Comptroller may direct the
Currency Manager to return digital assets to the Mint
for the express purpose of reducing the float. Digital assets
so delivered are to be deposited into the Mint account,
thus reducing the float by that amount.
The purchase, redemption and trading at Digitalis OT server
normally are done on the basis of strong privacy. We try to
never release any of your information unless compelled by law.
- -----BEGIN CERTIFICATE-----
MIICPzCCAaigAwIBAgIBADANBgkqhkiG9w0BAQQFADAlMQswCQYDVQQGEwJVSzEW
MBQGA1UEAxMNT3BlblNTTCBHcm91cDAeFw0xMTEyMDQwNTM2MjdaFw0yMTEyMDEw
NTM2MjdaMCUxCzAJBgNVBAYTAlVLMRYwFAYDVQQDEw1PcGVuU1NMIEdyb3VwMIGf
MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCvjeMKIacyh7LyVwaxHopSa0EY0SdD
hVeXRFQ+JyvRcTp2CBOFuUZ9mx7MgSyblaZssue/C6CdMtuJfabQgUHhK2zaArx6
rrvQ57SHH4p38xmVG8frD22pS4/wF+M2tmt6yCj9kxTLY6cWPve70gf1HE6sS4BJ
gl2uM8ZcDr5deQIDAQABo38wfTAPBgNVHRMBAf8EBTADAQH/MA4GA1UdDwEB/wQE
AwIBBjAdBgNVHQ4EFgQUBti7sfjamiXcNkp/WSir5iOauo0wEQYJYIZIAYb4QgEB
BAQDAgIEMCgGCWCGSAGG+EIBDQQbFhlleGFtcGxlIGNvbW1lbnQgZXh0ZW5zaW9u
MA0GCSqGSIb3DQEBBAUAA4GBAFZ4UxLkWRWvpcpqEs+jATB+2c1X7g2m00+7IXjv
2WG99F0I+ZGWmuowaxnzMAOmTNXFYplEKPYeoYjWaVOaqDq2L+bsaP6SxJDn/+wW
xGBJFBqNqzH8VkLQf/8lhuE8FMsX7H1k94Q2pACRGUZRRGaPlmV0fcx5/zCnhvcQ
wmkq
- -----END CERTIFICATE-----
-----BEGIN CONTRACT SIGNATURE-----
Version: Open Transactions 0.75
Comment: http://github.com/FellowTraveler/Open-Transactions/wiki
CoABFojWQphmaNv2WOIsGuvvqtO4zIJS74K9+rieHoeJ7jNu9SGFgPhvIPw84Ghi
ual/poyRK870Fs2y2T9dMctWiuj+D3+2bURcLfv/Kz3wXmldGfV9UAeYQhlVSkIv
BMyUqVu6LIIDle9CUFRICjNohX89qCr55b+Wqvcppbj7oEY=
-----END CONTRACT SIGNATURE-----
in he bash and since Enter isnt working as EOF in Windows i put a ~ in a blank line behind. Then enter.
Code:
It shows me Error in OTContract::ParseRawFile: EOF while reading xml content.
Sorry, failed. Are you sure that was a server contract?
Sorry, failed. Are you sure that was a server contract?
Is the server contract too old for the version of OT or is there a problem with copying the files content in windows?
By the way... how do i close OT without having to delete next time the file: ot.pid first in client_data to run OT?
Sorry for asking so much...
you should be pasting the entire otc file when doing addserver command.
Sounds like you should be using the otc file instead of the xml file.
If I were you, I wouldn't start with a real server. I would start with the localhost test server and copy over the test data. Play with it that way first before you start trying to talk to real servers.
If I were you, I wouldn't start with a real server. I would start with the localhost test server and copy over the test data. Play with it that way first before you start trying to talk to real servers.
I watched the videos and think i got a good enough overview about the possibilities of OT and because of the videos i can guess what the commands mean. (By the way... isnt there a man
Im not sure what you mean with otc and xml. I downloaded the otc file and inside its xml right? So can i use the file directly? The command addserver asks me to paste the contract directly only.
Jump to: