Bitcoin Forum
April 28, 2024, 10:43:43 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 [1769] 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 ... 2557 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2761529 times)
msin
Legendary
*
Offline Offline

Activity: 1470
Merit: 1004


View Profile
February 19, 2014, 04:57:24 PM
 #35361

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

Don't trust online wallets.

Just implement your own wallet app and make it opensource to let other contribute and audit the code base.

Agreed, just wanted to see what we have out there.  

Thanks Pin
1714301023
Hero Member
*
Offline Offline

Posts: 1714301023

View Profile Personal Message (Offline)

Ignore
1714301023
Reply with quote  #2

1714301023
Report to moderator
1714301023
Hero Member
*
Offline Offline

Posts: 1714301023

View Profile Personal Message (Offline)

Ignore
1714301023
Reply with quote  #2

1714301023
Report to moderator
1714301023
Hero Member
*
Offline Offline

Posts: 1714301023

View Profile Personal Message (Offline)

Ignore
1714301023
Reply with quote  #2

1714301023
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
barbierir
Hero Member
*****
Offline Offline

Activity: 515
Merit: 502



View Profile WWW
February 19, 2014, 05:02:01 PM
 #35362

I found this android wallet for Nxt, is it legit? I don't remember seeing it mentioned in this thread, on the forums, on nxtclient.org or anywhere else.

https://play.google.com/store/apps/details?id=org.nextcoin.nxtclient

◈▣ KOMODO ● Set Your Ideas Free ▣◈
.......AN ECOSYSTEM FOR NATIVE BLOCKCHAINS.......
Blockchain Generator | Decentralized Crowdfunding | Decentralized Exchange | Bitcoin Security | Zero-Knowledge Proofs | Blockchain Interoperability | Scalable Infrastructure
lophie
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1001

Unlimited Free Crypto


View Profile
February 19, 2014, 05:03:51 PM
 #35363

I found this android wallet for Nxt, is it legit? I don't remember seeing it mentioned in this thread, on the forums, on nxtclient.org or anywhere else.

https://play.google.com/store/apps/details?id=org.nextcoin.nxtclient

Yes and it is very awesome you can build it from source, it is available. I actually read some of the source it connects to other nodes to perform operations but it is safe because it does the signing locally, Now just ensure that YOUR PHONE is spyware free Wink

- Lophie

Will take me a while to climb up again, But where is a will, there is a way...
opticalcarrier
Full Member
***
Offline Offline

Activity: 238
Merit: 100



View Profile
February 19, 2014, 05:05:05 PM
 #35364


Don't trust online wallets.


THIS THIS THIS.  you can never fully trust online wallets!  EVEN IF they have SSL certs!  By trusting an online wallet you are trusting anyone who has access to the server.  Do you know how many people that is?  If its a VPS its even worse!

Best case is to wait for a javascript client that signs outbound transactions and polls public nodes for inbound transactions.  We REALLY need this, if this comes out....price will skyrocket.
POPPP
Jr. Member
*
Offline Offline

Activity: 54
Merit: 10


View Profile
February 19, 2014, 05:07:52 PM
 #35365

I would like to see Nxt's AE implement a social credit system.  This social credit system would allow people to issue micro loans and establish LETSystems in their communities.  LETSystems allow communities with no external capital or capital of their own to resurrect their own economy with an expanding/contracting credit system.

This idea is in-line with BCNext's vision of currencies built on top of Nxt.  I hope he would approve.

+1

In combination with reputation system(credit rating) micro-loans could be huge....well in the beginning for digital goods, gaming, etc.

that could be huge Smiley
abuelau
Hero Member
*****
Offline Offline

Activity: 750
Merit: 500


www.coinschedule.com


View Profile
February 19, 2014, 05:08:35 PM
 #35366

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

please define secure Grin in online.

maybe: https://wallet.mynxt.info/

I can provide information about the security of the wallet if necessary.

Know what's happening in cryptoworld: www.coinschedule.com
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 19, 2014, 05:11:36 PM
 #35367

is there an api call that returns all api calls, or is it possible to access the javadoc @ https://nxt.airdns.org:7875/doc/ to get a list of all api calls? I am a bit panicky on missing out on important things, e.g. as with the vote thingy, which I only just picked up en passant
There is no API to get them all, but in the javadoc each class under the nxt.http package handles exactly one API call. Unfortunately I haven't had the time to document their parameters and return values in the javadoc itself.
The javadoc is also available on your local node under webapps/root/doc.
It was CfB who added the voting system, and it is not enabled yet, so I didn't have much to say about it in the changelog.

lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
msin
Legendary
*
Offline Offline

Activity: 1470
Merit: 1004


View Profile
February 19, 2014, 05:13:42 PM
 #35368

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

please define secure Grin in online.

maybe: https://wallet.mynxt.info/

I can provide information about the security of the wallet if necessary.

Okay, please provide.
Jean-Luc
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250



View Profile WWW
February 19, 2014, 05:15:40 PM
 #35369

following errors in 7.6, but running


Code:
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.643] DEBUG: Invalid transaction attachment:
{"alias":"greenenergymarket","uri":""}
[2014-02-19 17:46:00.643] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6871
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.646] DEBUG: Invalid transaction attachment:
{"message":"d5664d4c6a788a6c639da093f952c1c87669aecbff05695fa62784251d639ddcc8cd
12a576de592ad929f3e035af881372b9a42e3a6310193fc486d51b408ecbadc79aa5260db0d55ad3
eda0db9acce23a1588881e9c141419e9baba43dde842"}
[2014-02-19 17:46:00.647] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Arbitrary messages not yet enabled at he
ight 6872
        at nxt.Transaction$Type$Messaging$1.validateAttachment(Transaction.java:
755)
        at nxt.Transaction$Type$Messaging$1.loadAttachment(Transaction.java:743)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.650] DEBUG: Invalid transaction attachment:
{"alias":"NRSrelease","uri":"http:\/\/download.nxtcrypto.org\/nxt-client-0.7.6.z
ip"}
[2014-02-19 17:46:00.650] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6872
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:00.653] DEBUG: Invalid transaction attachment:
{"alias":"NRSversion","uri":"0.7.6 c219d6a13c870ea7f454fe1e91efe6c6098bed767156a
a8921aad0bebe9fe79a"}
[2014-02-19 17:46:00.653] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 6873
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.216] DEBUG: Invalid transaction attachment:
{"alias":"distributedenergymarket","uri":""}
[2014-02-19 17:46:07.216] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8270
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.219] DEBUG: Invalid transaction attachment:
{"alias":"hkland","uri":""}
[2014-02-19 17:46:07.220] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8271
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.222] DEBUG: Invalid transaction attachment:
{"alias":"nxtgreenenergymarket","uri":""}
[2014-02-19 17:46:07.222] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8271
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.225] DEBUG: Invalid transaction attachment:
{"alias":"NXTCraft","uri":""}
[2014-02-19 17:46:07.226] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8272
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.229] DEBUG: Invalid transaction attachment:
{"alias":"NXTScape","uri":""}
[2014-02-19 17:46:07.230] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8272
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.233] DEBUG: Invalid transaction attachment:
{"alias":"greenenergymarket","uri":""}
[2014-02-19 17:46:07.233] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8273
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.236] DEBUG: Invalid transaction attachment:
{"message":"d5664d4c6a788a6c639da093f952c1c87669aecbff05695fa62784251d639ddcc8cd
12a576de592ad929f3e035af881372b9a42e3a6310193fc486d51b408ecbadc79aa5260db0d55ad3
eda0db9acce23a1588881e9c141419e9baba43dde842"}
[2014-02-19 17:46:07.236] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Arbitrary messages not yet enabled at he
ight 8274
        at nxt.Transaction$Type$Messaging$1.validateAttachment(Transaction.java:
755)
        at nxt.Transaction$Type$Messaging$1.loadAttachment(Transaction.java:743)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.239] DEBUG: Invalid transaction attachment:
{"alias":"NRSrelease","uri":"http:\/\/download.nxtcrypto.org\/nxt-client-0.7.6.z
ip"}
[2014-02-19 17:46:07.239] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8274
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:46:07.242] DEBUG: Invalid transaction attachment:
{"alias":"NRSversion","uri":"0.7.6 c219d6a13c870ea7f454fe1e91efe6c6098bed767156a
a8921aad0bebe9fe79a"}
[2014-02-19 17:46:07.242] DEBUG: Dropping invalid transaction
nxt.Transaction$NotYetEnabledException: Aliases not yet enabled at height 8275
        at nxt.Transaction$Type$Messaging$2.validateAttachment(Transaction.java:
831)
        at nxt.Transaction$Type$Messaging$2.loadAttachment(Transaction.java:801)

        at nxt.Transaction.getTransaction(Transaction.java:157)
        at nxt.Blockchain.processJSONTransactions(Blockchain.java:796)
        at nxt.Blockchain.access$000(Blockchain.java:40)
        at nxt.Blockchain$1.run(Blockchain.java:89)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
[2014-02-19 17:49:57.457] Checksum passed at block 30000
Again ignore, those are harmless, I forgot to comment out the debug logging. Throwing a NotYetEnabledException is the normal way that such errors are handled, and from the point of view of your node which is behind in loading the blockchain, those features are indeed not yet enabled. When it catches up with the current blockchain head, it will no longer consider those transactions invalid.


lead Nxt developer, gpg key id: 0x811D6940E1E4240C
Nxt blockchain platform | Ardor blockchain platform | Ignis ICO
abuelau
Hero Member
*****
Offline Offline

Activity: 750
Merit: 500


www.coinschedule.com


View Profile
February 19, 2014, 05:18:19 PM
 #35370

Can someone send me links to any secure online Nxt wallets available?  Working with a couple exchanges to add Nxt and want to make it easy for their end users.  Thanks.

please define secure Grin in online.

maybe: https://wallet.mynxt.info/

I can provide information about the security of the wallet if necessary.

Okay, please provide.

In short:

1) Nxt Account Private Keys are 50 chars randomly generated by cryptographic standard algorithm
2) Keys are AES 256 encrypted twice. One time using a site-wide private AES key and one time using the user's salted password.
3) Only SSL is allowed through the site

If an attacker ever gets on hold of my database, they won't be able to decrypt the account private keys without having both the user password AND the site-wide AES private key.

No system is 100% safe, we all know this. But I think this wallet is much safer than simply using brain wallets (as it is today). Humans are not very good in creating and then storing truly random passwords.

Know what's happening in cryptoworld: www.coinschedule.com
wesleyh
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
February 19, 2014, 05:19:20 PM
 #35371


Don't trust online wallets.


THIS THIS THIS.  you can never fully trust online wallets!  EVEN IF they have SSL certs!  By trusting an online wallet you are trusting anyone who has access to the server.  Do you know how many people that is?  If its a VPS its even worse!

Best case is to wait for a javascript client that signs outbound transactions and polls public nodes for inbound transactions.  We REALLY need this, if this comes out....price will skyrocket.

Umm isn't that what my client does ? http://nxtra.org/nxt-client (ok, it doesn't yet sign outbound transactions, but it's on my todo list :-))
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 05:19:53 PM
 #35372

In short:

1) Nxt Account Private Keys are 50 chars randomly generated by cryptographic standard algorithm
2) Keys are AES 256 encrypted twice. One time using a site-wide private AES key and one time using the user's salted password.
3) Only SSL is allowed through the site

If an attacker ever gets on hold of my database, they won't be able to decrypt the account private keys without having both the user password AND the site-wide AES private key.

No system is 100% safe, we all know this. But I think this wallet is much safer than simply using brain wallets (as it is today). Humans are not very good in creating and then storing truly random passwords.

Sounds good.

What is the cryptographic standard algorithm for creating the passwords?
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 05:23:08 PM
 #35373


Don't trust online wallets.


THIS THIS THIS.  you can never fully trust online wallets!  EVEN IF they have SSL certs!  By trusting an online wallet you are trusting anyone who has access to the server.  Do you know how many people that is?  If its a VPS its even worse!

Best case is to wait for a javascript client that signs outbound transactions and polls public nodes for inbound transactions.  We REALLY need this, if this comes out....price will skyrocket.

Umm isn't that what my client does ? http://nxtra.org/nxt-client (ok, it doesn't yet sign outbound transactions, but it's on my todo list :-))

Great. Smiley We would love to see it.
abuelau
Hero Member
*****
Offline Offline

Activity: 750
Merit: 500


www.coinschedule.com


View Profile
February 19, 2014, 05:23:25 PM
 #35374

In short:

1) Nxt Account Private Keys are 50 chars randomly generated by cryptographic standard algorithm
2) Keys are AES 256 encrypted twice. One time using a site-wide private AES key and one time using the user's salted password.
3) Only SSL is allowed through the site

If an attacker ever gets on hold of my database, they won't be able to decrypt the account private keys without having both the user password AND the site-wide AES private key.

No system is 100% safe, we all know this. But I think this wallet is much safer than simply using brain wallets (as it is today). Humans are not very good in creating and then storing truly random passwords.

Sounds good.

What is the cryptographic standard algorithm for creating the passwords?

Linux's urandom whch uses environmental noise from drivers to generate truly random numbers.

Know what's happening in cryptoworld: www.coinschedule.com
martismartis
Legendary
*
Offline Offline

Activity: 1162
Merit: 1005


View Profile
February 19, 2014, 05:24:31 PM
 #35375

Just to inform, 0.7.6 runs smoothly on Android TV stick public node.

For a while Smiley
lophie
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1001

Unlimited Free Crypto


View Profile
February 19, 2014, 05:25:33 PM
 #35376

Guys I have been thinking (<- typical  Roll Eyes).

If I am mining with alot of nxt and I wasn to send a transaction but I am okay if it takes the whole day to include, How about I DONT broadcast my transactions and just try to generate a block with my transactions + others. So whenever I find a block I will actually be sending NXT for free.

Is there any major flaws in this logic, I mean can anyone here point them out because sure there are plenty Tongue.

- Lophie

Will take me a while to climb up again, But where is a will, there is a way...
lophie
Hero Member
*****
Offline Offline

Activity: 924
Merit: 1001

Unlimited Free Crypto


View Profile
February 19, 2014, 05:26:15 PM
 #35377

Just to inform, 0.7.6 runs smoothly on Android TV stick public node.

For a while Smiley

Picuntu? Please share hardware and software information, I am VERY interested... I bricked a stick for this...

Will take me a while to climb up again, But where is a will, there is a way...
punkrock
Hero Member
*****
Offline Offline

Activity: 808
Merit: 1011



View Profile
February 19, 2014, 05:29:56 PM
 #35378

Unregistered users = 3 votes per hour!

>>>>>>>>>>>>>>> PLEASE VOTE! <<<<<<<<<<<<<<<

Registered users = 6 votes per hour!


Please quote me, share on Twitter, Facebook, Reddit... thanks!


BUY VOTES FOR NXT!

1 VOTE = 0,00005 BTC
1 BTC = 20,000 VOTES FOR NXT

Website: https://www.mintpal.com/voting
How to? Send any BTC to 1KB2AWLpKByBifkyQLJERhZi4jVDGWMA4n

Each 0.00005000 BTC received will count for 1 vote. All payment votes will be publicly visible, as you can see by clicking here.

wesleyh
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250


View Profile
February 19, 2014, 05:31:13 PM
 #35379

Unregistered users = 3 votes per hour!

>>>>>>>>>>>>>>> PLEASE VOTE! <<<<<<<<<<<<<<<

Registered users = 6 votes per hour!


Please quote me, share on Twitter, Facebook, Reddit... thanks!


BUY VOTES FOR NXT!

1 VOTE = 0,00005 BTC
1 BTC = 20,000 VOTES FOR NXT

Website: https://www.mintpal.com/voting
How to? Send any BTC to 1KB2AWLpKByBifkyQLJERhZi4jVDGWMA4n

Each 0.00005000 BTC received will count for 1 vote. All payment votes will be publicly visible, as you can see by clicking here.


You should change the message to say that you can actually click 3 times in a row. There appears to be no time limit in between.
ChuckOne
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250

☕ NXT-4BTE-8Y4K-CDS2-6TB82


View Profile
February 19, 2014, 05:31:17 PM
 #35380

In short:

1) Nxt Account Private Keys are 50 chars randomly generated by cryptographic standard algorithm
2) Keys are AES 256 encrypted twice. One time using a site-wide private AES key and one time using the user's salted password.
3) Only SSL is allowed through the site

If an attacker ever gets on hold of my database, they won't be able to decrypt the account private keys without having both the user password AND the site-wide AES private key.

No system is 100% safe, we all know this. But I think this wallet is much safer than simply using brain wallets (as it is today). Humans are not very good in creating and then storing truly random passwords.

Sounds good.

What is the cryptographic standard algorithm for creating the passwords?

Linux's urandom whch uses environmental noise from drivers to generate truly random numbers.

Thank you. Smiley

This should be the certificate fingerprints:

sha-256: 15 0B D5 E2 89 C9 73 4A D5 89 29 07 10 28 22 F4 4B 8F 9B 72 90 B9 58 AF 47 73 E7 98 7B BD 0C 79
sha-1: 88 5F 57 E9 93 51 F9 48 96 9F 1A 31 A6 B9 93 C9 8E 28 3E A0
issued on 2/2/14
expires on 2/3/15

I think that should be enough data for everyone to decide whether they trust you and the security of the server.

Am I right that the physical device is in the cloud?
Pages: « 1 ... 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 [1769] 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 ... 2557 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!