AlphaX/qortal
1
0
Fork 0
forked from Qortal/qortal
Code Issues Pull Requests Projects Releases Wiki Activity

Adjust Asset data max size to reflect HSQLDB CLOB size

Browse Source 
+ fix incorrect logic when calculating issue-asset transaction
data length
This commit is contained in:
catbref 2019-03-26 14:36:47 +00:00
parent d741580ccf
commit d3c1602d9b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/java/org/qora/asset/Asset.java
View File

@ -18,7 +18,7 @@ public class Asset {
public static final int MAX_NAME_SIZE = 400;
public static final int MAX_DESCRIPTION_SIZE = 4000;
public static final int MAX_DATA_SIZE = 4000;
public static final int MAX_DATA_SIZE = 400000;
public static final long MAX_DIVISIBLE_QUANTITY = 10_000_000_000L;
public static final long MAX_INDIVISIBLE_QUANTITY = 1_000_000_000_000_000_000L;

2
src/main/java/org/qora/transform/transaction/IssueAssetTransactionTransformer.java
View File

@ -103,7 +103,7 @@ public class IssueAssetTransactionTransformer extends TransactionTransformer {
+ Utf8.encodedLength(issueAssetTransactionData.getDescription());
// In v2, assets have "data" field
if (transactionData.getTimestamp() < BlockChain.getInstance().getQoraV2Timestamp())
if (transactionData.getTimestamp() >= BlockChain.getInstance().getQoraV2Timestamp())
dataLength += DATA_SIZE_LENGTH + Utf8.encodedLength(issueAssetTransactionData.getData());
// In v1, IssueAssetTransaction uses Asset.toBytes which also serializes